# CVE-2018-3053: Missing authorization in Retail Customer Management and Segmentation Foundation

> Low-privileged attackers can modify data and cause partial denial of service in Oracle Retail Customer Management and Segmentation Foundation via HTTP.

- **Severity:** Medium 6.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2018
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-g43v-j6q9-w688

## What is CVE-2018-3053?

CVE-2018-3053 is a medium-severity missing authorization vulnerability in Oracle Retail Customer Management and Segmentation Foundation, published on 18 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability in the Oracle Retail Customer Management and Segmentation Foundation component of Oracle Retail Applications (subcomponent: Internal Operations). Supported versions that are affected are 16.x and 17.x. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Retail Customer Management and Segmentation Foundation. While the vulnerability is in Oracle Retail Customer Management and Segmentation Foundation, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Retail Customer Management and Segmentation Foundation accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Retail Customer Management and Segmentation Foundation. CVSS 3.0 Base Score 6.4 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L).

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

It affects 1 product.


Products: Oracle Retail Customer Management and Segmentation Foundation.

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

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

## Is CVE-2018-3053 being exploited?

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

## Other vulnerabilities in Oracle Retail Customer Management and Segmentation Foundation

- [CVE-2020-2953](https://insights.sbomify.com/CVE-2020-2953/): Auth bypass in Retail Customer Management and Segmentation Foundation (critical 9.8)
- [CVE-2019-3772](https://insights.sbomify.com/CVE-2019-3772/): Spring Integration XML External Entity Injection (XXE) (critical 9.8)
- [CVE-2018-3315](https://insights.sbomify.com/CVE-2018-3315/): Missing authorization in Retail Customer Management and Segmentation Foundation (high 8.2)
- [CVE-2018-3316](https://insights.sbomify.com/CVE-2018-3316/): Missing authorization in Retail Customer Management and Segmentation Foundation (high 7.6)
- [CVE-2020-14709](https://insights.sbomify.com/CVE-2020-14709/): Missing authorization in Retail Customer Management and Segmentation Foundation (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-3053 is a medium-severity missing authorization vulnerability in Oracle Retail Customer Management and Segmentation Foundation, published on 18 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-3053 in the wild and no public exploit code.

Affected product: Oracle Retail Customer Management and Segmentation Foundation. 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-3053/ (Markdown: https://insights.sbomify.com/CVE-2018-3053/index.md)
```

## Sources

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

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