# CVE-2018-3181: Information disclosure in Hospitality Cruise Shipboard Property Management System

> A low-privileged attacker with local access can exploit this vulnerability to gain unauthorized access to all accessible data in the Oracle Hospitality Cruise Shipboard Property Management System.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2018
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-p8h5-68jv-57gj

## What is CVE-2018-3181?

CVE-2018-3181 is a medium-severity vulnerability in Oracle Corporation Hospitality Cruise Shipboard Property Management System, published on 17 Oct 2018. It can only be exploited from the same machine or local 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 ENOAD). The supported version that is affected is 8.0. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Hospitality Cruise Shipboard Property Management System executes to compromise Oracle Hospitality Cruise Shipboard Property Management System. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Hospitality Cruise Shipboard Property Management System accessible data. CVSS 3.0 Base Score 5.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).

## Which versions are affected by CVE-2018-3181?

It affects 1 product.


Products: Oracle Hospitality Cruise Shipboard Property Management System.

## How do I fix CVE-2018-3181?

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

## Is CVE-2018-3181 being exploited?

There is no known exploitation of CVE-2018-3181 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-2018-3181 and fix it if it is affected.

What it is: CVE-2018-3181 is a medium-severity vulnerability in Oracle Corporation Hospitality Cruise Shipboard Property Management System, published on 17 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3181 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-2018-3181/ (Markdown: https://insights.sbomify.com/CVE-2018-3181/index.md)
```

## Sources

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

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