# CVE-2021-35587: Oracle Fusion Middleware Unspecified

> Unauthenticated attackers can bypass authentication to take over Oracle Access Manager via HTTP, leading to full system compromise.

- **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 28 Nov 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-x3jv-936g-xqj4

## What is CVE-2021-35587?

CVE-2021-35587 is a critical authentication bypass vulnerability in Oracle Access Manager, published on 19 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Access Manager product of Oracle Fusion Middleware (component: OpenSSO Agent). Supported versions that are affected are 11.1.2.3.0, 12.2.1.3.0 and 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Access Manager. Successful attacks of this vulnerability can result in takeover of Oracle Access Manager. 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-2021-35587?

It affects 1 product.


Products: Oracle Access Manager.

## How do I fix CVE-2021-35587?

No fix has been published for CVE-2021-35587 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 19 Dec 2022.

## Is CVE-2021-35587 being exploited?

Yes. Attackers have exploited CVE-2021-35587 in the wild since at least 28 Nov 2022.

Public exploit code:

- Oracle Access Manager Unauthenticated Attacker Vulnerability CVE-2021-35587 (github_poc): https://github.com/ZZ-SOCMAP/CVE-2021-35587
- Oracle Access Manager unauthenticated Remote Code Execution (metasploit)
- Post-incident report analyzing the Oracle Cloud SSO/LDAP supply chain attack (CVE-2021-35587). Details the exploitation of legacy server infrastructure, impact across 140,000+ cloud tenants, root-cause findings, and phased mitigation strategies. (github_poc): https://github.com/Jwa7470/2025-Oracle-SSO-LDAP-Attack-Post-Incident-Written-Report
- Oracle Access Manager - Remote Code Execution (nuclei): http/cves/2021/CVE-2021-35587.yaml

## Other vulnerabilities in Oracle Access Manager

- [CVE-2020-2555](https://insights.sbomify.com/CVE-2020-2555/): Oracle Multiple Products Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2026-71133](https://insights.sbomify.com/CVE-2026-71133/): Auth bypass in Oracle Access Manager (critical 10.0)
- [CVE-2026-60358](https://insights.sbomify.com/CVE-2026-60358/): Auth bypass in Oracle Access Manager (critical 10.0)
- [CVE-2026-71163](https://insights.sbomify.com/CVE-2026-71163/): Missing authorization in Oracle Access Manager (critical 9.9)
- [CVE-2026-73945](https://insights.sbomify.com/CVE-2026-73945/): Auth bypass in Oracle Access Manager (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-35587 and fix it if it is affected.

What it is: CVE-2021-35587 is a critical authentication bypass vulnerability in Oracle Access Manager, published on 19 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2021-35587 in the wild since at least 28 Nov 2022.

Affected product: Oracle Access Manager. 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-2021-35587/ (Markdown: https://insights.sbomify.com/CVE-2021-35587/index.md)
```

## Sources

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

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