dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 19 Dec 2022.
Access ManagerApplication · Oracle

CVE-2021-35587

CRITICAL · 9.8 CVSS v3.1 Published 2022-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Oracle Access Manager's OpenSSO Agent component contains a critical vulnerability (CVSS 9.8) that allows unauthenticated attackers with network access via HTTP to completely compromise the affected system. The vulnerability affects versions 11.1.2.3.0, 12.2.1.3.0, and 12.2.1.4.0, enabling full confidentiality, integrity, and availability compromise leading to complete system takeover.

MitigationApply Oracle Critical Patch Update (CPU) for Oracle Access Manager addressing CVE-2021-35587. Until patch application, consider network segmentation and restricting HTTP/HTTPS access to the OpenSSO Agent interfaces to trusted sources only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Access ManagerApplication
Affected:= 11.1.2.3.0= 12.2.1.3.0= 12.2.1.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle Access Manager installation
    Locate the Oracle Access Manager installation directory and locate the version file or check the admin console for the product version information
    Affected if The installed version matches 11.1.2.3.0, 12.2.1.3.0, or 12.2.1.4.0 exactly
  2. Verify OpenSSO Agent component presence
    Check the Oracle Access Manager installation for the OpenSSO Agent component - this may be visible in the admin console under agent profiles or in the components directory within the installation
    Affected if The OpenSSO Agent component is installed and enabled in the Oracle Access Manager environment
  3. Confirm network exposure
    Determine if the Oracle Access Manager web interfaces are accessible over HTTP/HTTPS from untrusted networks
    Affected if The Oracle Access Manager interfaces are reachable via HTTP from network locations without authentication requirements

A user is affected if their Oracle Access Manager installation is version 11.1.2.3.0, 12.2.1.3.0, or 12.2.1.4.0 AND the OpenSSO Agent component is present and network-accessible without authentication barriers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) for Oracle Access Manager addressing CVE-2021-35587. Until patch application, consider network segmentation and restricting HTTP/HTTPS access to the OpenSSO Agent interfaces to trusted sources only.

Recommended fix High confidence

Upgrade to 12.2.1.4.0 with October 2021 CPU applied (or latest available 12.2.1.x version with all security patches)

  1. Check your current Oracle Access Manager version by logging into the OAM Administration Console or running the appropriate version command
  2. Apply Oracle Critical Patch Update October 2021 (or subsequent updates) which contains the fix for CVE-2021-35587
  3. For version 11.1.2.3.0: Apply patch 33416152 or upgrade to 11.1.2.3.x (latest available 11.1.2.3.x patch)
  4. For version 12.2.1.3.0: Apply patch 33416152 or upgrade to 12.2.1.4.0 and apply all subsequent security patches
  5. For version 12.2.1.4.0: Apply patch 33416152 and all subsequent security patches
  6. After patching, verify the OpenSSO Agent component is properly configured and functioning
  7. Review Oracle Access Manager audit logs to confirm no exploitation occurred prior to patching
Caveat Oracle CPU patches are cumulative; apply in a test environment first to verify compatibility with existing integrations and custom configurations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Access Manager Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-35587 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-35587 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data