# CVE-2019-2410: Missing authorization in Hospitality Cruise Shipboard Property Management System

> Unauthenticated local attackers can read and modify data in Oracle Hospitality Cruise Shipboard Property Management System due to missing authorization checks.

- **Severity:** Medium 5.1 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2019
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-wgx9-ggvp-ch4q

## What is CVE-2019-2410?

CVE-2019-2410 is a medium-severity missing authorization vulnerability in Oracle Corporation Hospitality Cruise Shipboard Property Management System, published on 16 Jan 2019. 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: DGS RES Online, FMS Sender, FMS Receiver, OHC WPF Security). The supported version that is affected is 8.0.8. Easily exploitable vulnerability allows unauthenticated 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 update, insert or delete access to some of Oracle Hospitality Cruise Shipboard Property Management System accessible data as well as unauthorized read access to a subset of Oracle Hospitality Cruise Shipboard Property Management System accessible data. CVSS 3.0 Base Score 5.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N).

## Which versions are affected by CVE-2019-2410?

It affects 1 product.


Products: Oracle Hospitality Cruise Shipboard Property Management System.

## How do I fix CVE-2019-2410?

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

## Is CVE-2019-2410 being exploited?

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

What it is: CVE-2019-2410 is a medium-severity missing authorization vulnerability in Oracle Corporation Hospitality Cruise Shipboard Property Management System, published on 16 Jan 2019. 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-2019-2410 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-2019-2410/ (Markdown: https://insights.sbomify.com/CVE-2019-2410/index.md)
```

## Sources

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

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