# CVE-2017-10097: Cross-site scripting in Hospitality Reporting and Analytics

> Unauthenticated attackers can exploit a cross-site scripting flaw in Oracle Hospitality Reporting to modify or read data via HTTP.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Aug 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-m58r-6f5c-7cf4

## What is CVE-2017-10097?

CVE-2017-10097 is a medium-severity cross-site scripting vulnerability in Oracle Corporation Hospitality Reporting and Analytics, published on 8 Aug 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Hospitality Reporting and Analytics component of Oracle Hospitality Applications (subcomponent: Reporting). Supported versions that are affected are 8.5.1 and 9.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Hospitality Reporting and Analytics. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Hospitality Reporting and Analytics, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Hospitality Reporting and Analytics accessible data as well as unauthorized read access to a subset of Oracle Hospitality Reporting and Analytics accessible data. CVSS 3.0 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

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

It affects 1 product.


Products: Oracle Hospitality Reporting and Analytics.

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

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

## Is CVE-2017-10097 being exploited?

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

## Other vulnerabilities in Oracle Corporation Hospitality Reporting and Analytics

- [CVE-2017-10402](https://insights.sbomify.com/CVE-2017-10402/): Auth bypass in Hospitality Reporting and Analytics (critical 10.0)
- [CVE-2017-10405](https://insights.sbomify.com/CVE-2017-10405/): Information disclosure in Hospitality Reporting and Analytics (critical 10.0)
- [CVE-2017-10404](https://insights.sbomify.com/CVE-2017-10404/): Auth bypass in Hospitality Reporting and Analytics (critical 9.9)
- [CVE-2023-21828](https://insights.sbomify.com/CVE-2023-21828/): Missing authorization in Hospitality Reporting and Analytics (high 8.1)
- [CVE-2021-2395](https://insights.sbomify.com/CVE-2021-2395/): Missing authorization in Hospitality Reporting and Analytics (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10097 is a medium-severity cross-site scripting vulnerability in Oracle Corporation Hospitality Reporting and Analytics, published on 8 Aug 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-10097 in the wild and no public exploit code.

Affected product: Oracle Corporation Hospitality Reporting and Analytics. 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-10097/ (Markdown: https://insights.sbomify.com/CVE-2017-10097/index.md)
```

## Sources

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

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