# CVE-2022-21587: Oracle E-Business Suite Unspecified

> Unauthenticated attackers can bypass authentication to take over Oracle Web Applications Desktop Integrator via HTTP.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 2 Feb 2023 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-64x7-wh2p-524g

## What is CVE-2022-21587?

CVE-2022-21587 is a critical authentication bypass vulnerability in Oracle E-Business Suite, published on 18 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Web Applications Desktop Integrator product of Oracle E-Business Suite (component: Upload). Supported versions that are affected are 12.2.3-12.2.11. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Web Applications Desktop Integrator. Successful attacks of this vulnerability can result in takeover of Oracle Web Applications Desktop Integrator. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2022-21587?

It affects 1 product.


Products: Oracle E-Business Suite.

## How do I fix CVE-2022-21587?

No fix has been published for CVE-2022-21587 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 23 Feb 2023.

## Is CVE-2022-21587 being exploited?

Yes. Attackers have exploited CVE-2022-21587 in the wild since at least 2 Feb 2023, including in ransomware campaigns.

Public exploit code:

- CVE-2022-21587 POC  (github_poc): https://github.com/hieuminhnv/CVE-2022-21587-POC
- This script is used for automating exploit for Oracle Ebussiness (EBS) for CVE 2022-21587 ( Unauthenticated File Upload For Remote Code Execution) (github_poc): https://github.com/sahabrifki/CVE-2022-21587-Oracle-EBS-
- Oracle E-BS CVE-2022-21587 Exploit (github_poc): https://github.com/rockmelodies/Oracle-E-BS-CVE-2022-21587-Exploit
- Oracle E-Business Suite (EBS) Unauthenticated Arbitrary File Upload (metasploit)
- Oracle E-Business Suite 12.2.3 -12.2.11 - Remote Code Execution (nuclei): http/cves/2022/CVE-2022-21587.yaml

## Other vulnerabilities in Oracle E-Business Suite

- [CVE-2026-46817](https://insights.sbomify.com/CVE-2026-46817/): Oracle E-Business Suite Improper Privilege Management (critical 9.8, exploited in the wild)
- [CVE-2015-4798](https://insights.sbomify.com/CVE-2015-4798/): Other in n/a (critical 10.0)
- [CVE-2015-4839](https://insights.sbomify.com/CVE-2015-4839/): Other in n/a (critical 10.0)
- [CVE-2008-1826](https://insights.sbomify.com/CVE-2008-1826/): Other in n/a (critical 10.0)
- [CVE-2007-5528](https://insights.sbomify.com/CVE-2007-5528/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-21587 and fix it if it is affected.

What it is: CVE-2022-21587 is a critical authentication bypass vulnerability in Oracle E-Business Suite, published on 18 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-21587 in the wild since at least 2 Feb 2023, including in ransomware campaigns.

Affected product: Oracle E-Business Suite. 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-2022-21587/ (Markdown: https://insights.sbomify.com/CVE-2022-21587/index.md)
```

## Sources

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

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