# CVE-2017-10361: Information disclosure in Hospitality Cruise Shipboard Property Management System

> Low-privileged attackers can read sensitive data and cause partial denial of service in Oracle Hospitality Cruise Shipboard Property Management System via HTTP.

- **Severity:** Medium 6.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-72fv-23pv-v692

## What is CVE-2017-10361?

CVE-2017-10361 is a medium-severity vulnerability in Oracle Corporation Hospitality Cruise Shipboard Property Management System, published on 19 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Oracle Hospitality Cruise Shipboard Property Management System component of Oracle Hospitality Applications (subcomponent: OHC DRS). The supported version that is affected is 8.0.2.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Hospitality Cruise Shipboard Property Management System. While the vulnerability is in Oracle Hospitality Cruise Shipboard Property Management System, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Hospitality Cruise Shipboard Property Management System accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Hospitality Cruise Shipboard Property Management System. CVSS 3.0 Base Score 6.4 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:L).

## Which versions are affected by CVE-2017-10361?

It affects 1 product.


Products: Oracle Hospitality Cruise Shipboard Property Management System.

## How do I fix CVE-2017-10361?

No fix has been published for CVE-2017-10361 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-10361 being exploited?

There is no known exploitation of CVE-2017-10361 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Corporation Hospitality Cruise Shipboard Property Management System

- [CVE-2018-2621](https://insights.sbomify.com/CVE-2018-2621/): Missing authorization in Hospitality Cruise Shipboard Property Management System (high 8.2)
- [CVE-2018-3160](https://insights.sbomify.com/CVE-2018-3160/): Privilege escalation in Hospitality Cruise Shipboard Property Management System (high 7.7)
- [CVE-2019-2411](https://insights.sbomify.com/CVE-2019-2411/): Denial of service in Hospitality Cruise Shipboard Property Management System (high 7.6)
- [CVE-2018-3000](https://insights.sbomify.com/CVE-2018-3000/): Information disclosure in Hospitality Cruise Shipboard Property Management System (high 7.1)
- [CVE-2019-2409](https://insights.sbomify.com/CVE-2019-2409/): Denial of service in Hospitality Cruise Shipboard Property Management System (medium 6.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-10361 and fix it if it is affected.

What it is: CVE-2017-10361 is a medium-severity vulnerability in Oracle Corporation Hospitality Cruise Shipboard Property Management System, published on 19 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10361 in the wild and no public exploit code.

Affected product: Oracle Corporation Hospitality Cruise Shipboard Property Management System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-10361/ (Markdown: https://insights.sbomify.com/CVE-2017-10361/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-10361
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-10361
- OSV: https://osv.dev/vulnerability/CVE-2017-10361

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-10361/
Summaries are generated and may contain mistakes; the official description above is the record.