# CVE-2017-10401: Missing authorization in Hospitality Cruise Materials Management

> Low-privileged attackers can modify, delete, or read critical data and cause denial of service in Oracle Hospitality Cruise Materials Management.

- **Severity:** High 8.7 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H`)
- **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:** 19 Oct 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-q9h4-x42c-56vh

## What is CVE-2017-10401?

CVE-2017-10401 is a high-severity missing authorization vulnerability in Oracle Corporation Hospitality Cruise Materials Management, published on 19 Oct 2017. 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 Materials Management component of Oracle Hospitality Applications (subcomponent: MMSUpdater). The supported version that is affected is 7.30.564.0. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Hospitality Cruise Materials Management executes to compromise Oracle Hospitality Cruise Materials Management. While the vulnerability is in Oracle Hospitality Cruise Materials Management, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Hospitality Cruise Materials Management accessible data as well as unauthorized read access to a subset of Oracle Hospitality Cruise Materials Management accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Hospitality Cruise Materials Management. CVSS 3.0 Base Score 8.7 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H).

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

It affects 1 product.


Products: Oracle Hospitality Cruise Materials Management.

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

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

## Is CVE-2017-10401 being exploited?

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

## Other vulnerabilities in Oracle Corporation Hospitality Cruise Materials Management

- [CVE-2017-10229](https://insights.sbomify.com/CVE-2017-10229/): Missing authorization in Hospitality Cruise Materials Management (medium 5.4)
- [CVE-2017-10054](https://insights.sbomify.com/CVE-2017-10054/): Missing authorization in Hospitality Cruise Materials Management (medium 5.1)
- [CVE-2020-2599](https://insights.sbomify.com/CVE-2020-2599/): Information disclosure in Hospitality Cruise Materials Management (medium 4.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10401 is a high-severity missing authorization vulnerability in Oracle Corporation Hospitality Cruise Materials Management, published on 19 Oct 2017. 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-2017-10401 in the wild and no public exploit code.

Affected product: Oracle Corporation Hospitality Cruise Materials Management. 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-10401/ (Markdown: https://insights.sbomify.com/CVE-2017-10401/index.md)
```

## Sources

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

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