CVE-2021-2137
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 · uneditedVulnerability in the Enterprise Manager Base Platform product of Oracle Enterprise Manager (component: Policy Framework). Supported versions that are affected are 13.4.0.0 and 13.5.0.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Enterprise Manager Base Platform. Successful attacks of this vulnerability can result in takeover of Enterprise Manager Base Platform. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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 · high confidenceVulnerability in Oracle Enterprise Manager Base Platform's Policy Framework component allows a low-privileged attacker with network access via HTTP to execute arbitrary code and achieve complete system takeover, impacting confidentiality, integrity, and availability.
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= 13.4.0.0= 13.5.0.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle Enterprise Manager Base Platform versionQuery the Enterprise Manager console or check the installation directory for the version file. Common locations include $ORACLE_HOME/EMGC_ Domain1/emsdk or the console's 'About' page which displays the installed version.Affected if The installed version matches exactly 13.4.0.0 or 13.5.0.0
-
Verify Policy Framework component is presentCheck the Enterprise Manager console under 'Enterprise' > 'Quality of Service Management' or navigate to the Policy Framework section within the Oracle Enterprise Manager Cloud Control interface.Affected if The Policy Framework module is accessible and listed in the console, indicating the vulnerable component is installed.
-
Confirm network accessibility of Enterprise Manager HTTP interfacesReview network configuration and firewall rules to determine if Enterprise Manager console ports (typically 7801-7803, or 5500 for Cloud Control) are exposed to untrusted networks. Use 'netstat -an | grep <port>' or review load balancer/firewall ACLs.Affected if HTTP-based interfaces are reachable from network segments accessible to low-privileged users or untrusted networks.
-
Check for existing exploit indicatorsReview Enterprise Manager audit logs and access logs for unusual requests to Policy Framework endpoints, particularly POST requests to policy execution or deployment functions.Affected if Suspicious activity patterns are found in logs related to Policy Framework operations from unexpected sources.
You are affected if your Enterprise Manager Base Platform is exactly version 13.4.0.0 or 13.5.0.0 AND the Policy Framework is accessible AND the HTTP interfaces are network-reachable by low-privileged attackers.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply Oracle Critical Patch Update (CPU) containing the fix for CVE-2021-2137 to affected versions 13.4.0.0 and 13.5.0.0. If immediate patching is not possible, restrict network access to Enterprise Manager interfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-2137 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-2137 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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