# CVE-2024-20949: Other in Customer Interaction History

> Unauthenticated attackers can read and modify data in Oracle Customer Interaction History via HTTP, requiring user interaction.

- **Severity:** Medium 6.1 (`CVSS:3.1/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:** 17 Feb 2024
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-4rgm-c3r2-2hwv

## What is CVE-2024-20949?

CVE-2024-20949 is a medium-severity vulnerability in Oracle Corporation Customer Interaction History, published on 17 Feb 2024. 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 Customer Interaction History product of Oracle E-Business Suite (component: Outcome-Result).  Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Customer Interaction History.  Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Customer Interaction History, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in  unauthorized update, insert or delete access to some of Oracle Customer Interaction History accessible data as well as  unauthorized read access to a subset of Oracle Customer Interaction History accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts).  CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2024-20949?

It affects 1 product.


Products: Oracle Customer Interaction History.

## How do I fix CVE-2024-20949?

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

## Is CVE-2024-20949 being exploited?

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

## Other vulnerabilities in Oracle Corporation Customer Interaction History

- [CVE-2021-2105](https://insights.sbomify.com/CVE-2021-2105/): Information disclosure in Customer Interaction History (high 8.2)
- [CVE-2021-2106](https://insights.sbomify.com/CVE-2021-2106/): Information disclosure in Customer Interaction History (high 8.2)
- [CVE-2021-2107](https://insights.sbomify.com/CVE-2021-2107/): Information disclosure in Customer Interaction History (high 8.2)
- [CVE-2020-2873](https://insights.sbomify.com/CVE-2020-2873/): Cross-site scripting in Customer Interaction History (high 8.2)
- [CVE-2018-3189](https://insights.sbomify.com/CVE-2018-3189/): Cross-site scripting in Customer Interaction History (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-20949 and fix it if it is affected.

What it is: CVE-2024-20949 is a medium-severity vulnerability in Oracle Corporation Customer Interaction History, published on 17 Feb 2024. 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-2024-20949 in the wild and no public exploit code.

Affected product: Oracle Corporation Customer Interaction History. 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-2024-20949/ (Markdown: https://insights.sbomify.com/CVE-2024-20949/index.md)
```

## Sources

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

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