Enterprise Manager Base PlatformApplication · Oracle

CVE-2022-21516

HIGH · 7.3 CVSS v3.1 Published 2022-07-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 Enterprise Manager Base Platform product of Oracle Enterprise Manager (component: Enterprise Manager Install). Supported versions that are affected are 13.4.0.0 and 13.5.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Enterprise Manager Base Platform. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Enterprise Manager Base Platform accessible data as well as unauthorized read access to a subset of Enterprise Manager Base Platform accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Enterprise Manager Base Platform. CVSS 3.1 Base Score 7.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L).

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 confidence

Oracle Enterprise Manager Base Platform contains an unauthenticated vulnerability in the Enterprise Manager Install component. An attacker with network access via HTTP can exploit this flaw to achieve unauthorized read, insert, update, or delete access to certain data, as well as cause a partial denial of service. The vulnerability affects versions 13.4.0.0 and 13.5.0.0 and is easily exploitable given the no-auth-required attack vector.

MitigationApply the Oracle Critical Patch Update that addresses CVE-2022-21516, or upgrade to a patched version of Enterprise Manager Base Platform beyond 13.5.0.0. Restrict network exposure of the Enterprise Manager console to trusted users only as an interim control.

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
Enterprise Manager Base PlatformApplication
Affected:= 13.4.0.0= 13.5.0.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
Low
Integrity
Low
Availability
Low

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

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 if Oracle Enterprise Manager Base Platform is installed
    Check for the presence of Oracle Enterprise Manager installation directories or look for the 'emctl' command-line utility typically located in $ORACLE_HOME/bin. On Windows, check Program Files for Oracle folders or look for Enterprise Manager services in Windows Services.
    Affected if Oracle Enterprise Manager Base Platform is found on the system
  2. Determine the installed version of Enterprise Manager
    Run 'emctl status -version' or 'emctl getversion' from the Oracle Home bin directory. Alternatively, check the Oracle inventory file (inventory.xml) or the EMgcDB directory for version files.
    Affected if The installed version is exactly 13.4.0.0 or exactly 13.5.0.0
  3. Verify the Enterprise Manager Install component is exposed
    Check if the Enterprise Manager console HTTP/HTTPS ports (typically 7801-7803 or 5500) are listening and accessible from the network. Use 'netstat -an | grep -E "7801|7802|7803|5500"' or equivalent to identify listening ports.
    Affected if The Enterprise Manager console ports are exposed to untrusted network access
  4. Confirm the vulnerability is network-exploitable
    Review firewall rules and network ACLs to determine if the Enterprise Manager HTTP endpoints (usually /em/console) are accessible without authentication from outside trusted networks.
    Affected if The console is reachable via HTTP from untrusted networks without authentication

A user is affected if Oracle Enterprise Manager Base Platform version 13.4.0.0 or 13.5.0.0 is installed and its HTTP console is network-accessible without authentication.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle Critical Patch Update that addresses CVE-2022-21516, or upgrade to a patched version of Enterprise Manager Base Platform beyond 13.5.0.0. Restrict network exposure of the Enterprise Manager console to trusted users only as an interim control.

Fix this in Enterprise Manager Base Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21516 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21516 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