HTTP ServerWeb server / proxy · Oracle

CVE-2024-20991

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 HTTP Server product of Oracle Fusion Middleware (component: Web Listener). The supported version that is affected is 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle HTTP Server. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle HTTP Server accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).

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 HTTP Server Web Listener component has an information disclosure vulnerability allowing unauthenticated network attackers via HTTP to read a subset of accessible data. This is a confidentiality-only impact (C:L) with no integrity or availability effects.

MitigationApply the latest Oracle Critical Patch Update (CPU) or security patch for Oracle HTTP Server version 12.2.1.4.0 from Oracle Support. If immediate patching is not possible, restrict network access to the Web Listener via firewall or ACL rules.

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
HTTP ServerWeb server / proxy
Affected:= 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
Low
Integrity
None
Availability
None

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

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 HTTP Server version
    Run 'opmnctl status -l' or check the Oracle Inventory, or look at the installation directory path which typically contains the version like $ORACLE_HOME/Oracle_Home/oracle_common/jdk/bin/java -version or check the OPatch lspatches output
    Affected if The installed version is exactly 12.2.1.4.0
  2. Confirm Web Listener component is in use
    Check if OHS is configured with mod_wl_ohs (Web Listener) by examining the httpd.conf or the component config in $ORACLE_HOME/Oracle_Home/ohs/config/httpd.conf, looking for Listen directives and module loading
    Affected if The Web Listener module (mod_wl_ohs) is loaded and configured with a Listen directive for HTTP access
  3. Verify HTTP listener network accessibility
    Check the Listen and VirtualHost directives in httpd.conf to determine binding address (0.0.0.0 indicates external exposure, 127.0.0.1 is local-only), and verify firewall rules allow external HTTP access on port 80/443
    Affected if The Web Listener binds to 0.0.0.0 or a public IP and is accessible from untrusted networks (not localhost-only or ACL-restricted)
  4. Review access logs for suspicious read patterns
    Examine access logs in $ORACLE_HOME/ohs/logs/access_log for unusual or unauthorized data access requests, particularly repeated requests to sensitive endpoints
    Affected if Unauthenticated external IP addresses are successfully reading data from the server via HTTP requests

You are affected if Oracle HTTP Server version 12.2.1.4.0 is running with its Web Listener exposed to network access, allowing unauthenticated attackers to read accessible data via HTTP.

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 latest Oracle Critical Patch Update (CPU) or security patch for Oracle HTTP Server version 12.2.1.4.0 from Oracle Support. If immediate patching is not possible, restrict network access to the Web Listener via firewall or ACL rules.

Fix this in HTTP Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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