Enterprise Manager Base PlatformApplication · Oracle

CVE-2024-20917

HIGH · 7.5 CVSS v3.1 Published 2024-02-17
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

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 Enterprise Manager Base Platform product of Oracle Enterprise Manager (component: Log Management). The supported version that is affected is 13.5.0.0. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Enterprise Manager Base Platform. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Enterprise Manager Base Platform, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Enterprise Manager Base Platform accessible data as well as unauthorized update, insert or delete access to some of Oracle Enterprise Manager Base Platform accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Enterprise Manager Base Platform. CVSS 3.1 Base Score 7.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/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 · moderate confidence

Vulnerability in Oracle Enterprise Manager Base Platform's Log Management component (13.5.0.0) allows unauthenticated remote attackers via HTTP to access or modify critical data, with potential scope change impacting additional products. Exploitation requires human interaction and high complexity, with high confidentiality impact but lower integrity and availability impacts.

MitigationApply Oracle Critical Patch Update (CPU) containing the fix for CVE-2024-20917. As a compensating control, restrict network access to Oracle Enterprise Manager interfaces and monitor for anomalous log management activity.

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.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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/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 Oracle Enterprise Manager installation
    Locate Oracle Enterprise Manager Base Platform installation directory or check installed products on the system
    Affected if Oracle Enterprise Manager Base Platform is not installed on the system
  2. Verify installed version
    Check the installed version of Oracle Enterprise Manager Base Platform against 13.5.0.0 using Oracle inventory or version detection methods
    Affected if The installed version is exactly 13.5.0.0
  3. Confirm Log Management component is in use
    Check if the Log Management component is configured or enabled within Oracle Enterprise Manager 13.5.0.0
    Affected if Log Management component is enabled or configured in the installation
  4. Check HTTP interface exposure
    Inspect Oracle Enterprise Manager HTTP listener configuration to determine if it accepts remote connections
    Affected if HTTP interface is accessible from network locations rather than localhost only

A system is affected if Oracle Enterprise Manager Base Platform version 13.5.0.0 is installed with Log Management component enabled and HTTP interface exposed to network attackers.

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) containing the fix for CVE-2024-20917. As a compensating control, restrict network access to Oracle Enterprise Manager interfaces and monitor for anomalous log management activity.

Recommended fix Moderate confidence

Apply Oracle CPU (Critical Patch Update) - the January 2024 CPU or later contains the fix. Specific patch numbers can be obtained from Oracle Support.

  1. Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2024-20917. For this CVE (January 2024), apply the January 2024 CPU or a later Oracle Critical Patch Update.
  2. After applying the CPU, verify the patch was successfully installed by checking the Oracle Enterprise Manager console and reviewing patch inventory.
  3. Consult Oracle Support Document 249212.1 for detailed patch application instructions specific to Enterprise Manager Base Platform.
  4. Restart Enterprise Manager services as required by the patch installation instructions.
Caveat Patches should be tested in a non-production environment before production deployment; Oracle CPU patches are cumulative and may include other fixes that could affect behavior.

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

Fix this in Enterprise Manager Base Platform Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20917 — 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-2024-20917 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