# CVE-2018-2993: Information disclosure in CRM Technical Foundation

> Unauthenticated attackers can access critical data and modify some records in Oracle CRM Technical Foundation via HTTP, requiring user interaction.

- **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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:** 18 Jul 2018
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-9f9f-hjmh-g96m

## What is CVE-2018-2993?

CVE-2018-2993 is a high-severity vulnerability in Oracle Corporation CRM Technical Foundation, published on 18 Jul 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 CRM Technical Foundation component of Oracle E-Business Suite (subcomponent: Preferences). Supported versions that are affected are 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5, 12.2.6 and 12.2.7. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle CRM Technical Foundation. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle CRM Technical Foundation, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle CRM Technical Foundation accessible data as well as unauthorized update, insert or delete access to some of Oracle CRM Technical Foundation accessible data. CVSS 3.0 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N).

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

It affects 1 product.


Products: Oracle Customer Relationship Management Technical Foundation.

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

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

## Is CVE-2018-2993 being exploited?

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

## Other vulnerabilities in Oracle Corporation CRM Technical Foundation

- [CVE-2020-14850](https://insights.sbomify.com/CVE-2020-14850/): Information disclosure in CRM Technical Foundation (high 8.2)
- [CVE-2020-2881](https://insights.sbomify.com/CVE-2020-2881/): Information disclosure in CRM Technical Foundation (high 8.2)
- [CVE-2020-2651](https://insights.sbomify.com/CVE-2020-2651/): Information disclosure in CRM Technical Foundation (high 8.2)
- [CVE-2020-2652](https://insights.sbomify.com/CVE-2020-2652/): Cross-site scripting in CRM Technical Foundation (high 8.2)
- [CVE-2020-2653](https://insights.sbomify.com/CVE-2020-2653/): Cross-site scripting in CRM Technical Foundation (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-2993 is a high-severity vulnerability in Oracle Corporation CRM Technical Foundation, published on 18 Jul 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-2993 in the wild and no public exploit code.

Affected product: Oracle Corporation CRM Technical 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-2993/ (Markdown: https://insights.sbomify.com/CVE-2018-2993/index.md)
```

## Sources

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

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