# CVE-2020-2567: Missing authorization in Retail Customer Management and Segmentation Foundation

> High-privileged attackers can modify or read data in Oracle Retail Customer Management via HTTP, requiring user interaction.

- **Severity:** Medium 4.8 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jan 2020
- **Updated:** 30 Sep 2024
- **Also known as:** GHSA-g2wr-f37h-4p5j

## What is CVE-2020-2567?

CVE-2020-2567 is a medium-severity missing authorization vulnerability in Oracle Retail Customer Management and Segmentation Foundation, published on 15 Jan 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the Oracle Retail Customer Management and Segmentation Foundation product of Oracle Retail Applications (component: Security). The supported version that is affected is 18.0. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle Retail Customer Management and Segmentation Foundation. Successful attacks require human interaction from a person other than the attacker and 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 as well as unauthorized read access to a subset of Oracle Retail Customer Management and Segmentation Foundation accessible data. CVSS 3.0 Base Score 4.8 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N).

## Which versions are affected by CVE-2020-2567?

It affects 1 product.


Products: Oracle Retail Customer Management and Segmentation Foundation.

## How do I fix CVE-2020-2567?

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

## Is CVE-2020-2567 being exploited?

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

What it is: CVE-2020-2567 is a medium-severity missing authorization vulnerability in Oracle Retail Customer Management and Segmentation Foundation, published on 15 Jan 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-2567 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-2020-2567/ (Markdown: https://insights.sbomify.com/CVE-2020-2567/index.md)
```

## Sources

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

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