# CVE-2018-2840: Information disclosure in Retail Xstore Point of Service

> Unauthenticated attackers can access critical data, modify records, and cause partial denial of service in Oracle Retail Xstore POS via HTTP.

- **Severity:** High 7.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L`)
- **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:** 19 Apr 2018
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-j8hq-225h-rwqf

## What is CVE-2018-2840?

CVE-2018-2840 is a high-severity vulnerability in Oracle Retail Xstore Point of Service, published on 19 Apr 2018. 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 Retail Xstore Point of Service component of Oracle Retail Applications (subcomponent: Xstore Office). Supported versions that are affected are 6.5.11, 7.0.6, 7.1.6, 15.0.1 and 16.0.2. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Retail Xstore Point of Service. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Retail Xstore Point of Service accessible data as well as unauthorized update, insert or delete access to some of Oracle Retail Xstore Point of Service accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Retail Xstore Point of Service. CVSS 3.0 Base Score 7.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L).

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

It affects 1 product.


Products: Oracle Retail Xstore Point of Service.

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

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

## Is CVE-2018-2840 being exploited?

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

## Other vulnerabilities in Oracle Retail Xstore Point of Service

- [CVE-2017-10214](https://insights.sbomify.com/CVE-2017-10214/): Missing authorization in Retail Xstore Point of Service (high 8.2)
- [CVE-2018-3126](https://insights.sbomify.com/CVE-2018-3126/): Auth bypass in Retail Xstore Point of Service (medium 6.6)
- [CVE-2017-10427](https://insights.sbomify.com/CVE-2017-10427/): Other in Retail Xstore Point of Service (medium 6.5)
- [CVE-2017-10183](https://insights.sbomify.com/CVE-2017-10183/): Other in Retail Xstore Point of Service (medium 6.5)
- [CVE-2016-3429](https://insights.sbomify.com/CVE-2016-3429/): Other in n/a (medium 4.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-2840 and fix it if it is affected.

What it is: CVE-2018-2840 is a high-severity vulnerability in Oracle Retail Xstore Point of Service, published on 19 Apr 2018. 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-2018-2840 in the wild and no public exploit code.

Affected product: Oracle Retail Xstore Point of Service. 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-2840/ (Markdown: https://insights.sbomify.com/CVE-2018-2840/index.md)
```

## Sources

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

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