dbcve.org
HTTP ServerWeb server / proxy · Oracle

CVE-2025-21498

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-21
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: Core). 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

CVE-2025-21498 is an information disclosure vulnerability in Oracle HTTP Server 12.2.1.4.0 affecting the Core component. The vulnerability allows unauthenticated remote attackers with network access via HTTP to read a subset of accessible data, with low confidentiality impact based on the CVSS vector indicating read-only access without authentication or complexity barriers.

MitigationApply the relevant Oracle Critical Patch Update for Oracle HTTP Server 12.2.1.4.0. Until a patch is available, restrict network access to Oracle HTTP Server endpoints using firewall rules or network segmentation, and monitor for unusual read access patterns.

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 installation location
    Locate the Oracle HTTP Server installation by checking for the 'Oracle_Home' directory or searching for 'ohs' binary paths, typically found under /u01/app/oracle/product/ or similar Oracle installation directories.
    Affected if Oracle HTTP Server is installed in the environment
  2. Determine installed OHS version
    Run 'opmnctl status -v' or check the version file in the OHS instance directory, or use 'httpd -v' if the OHS HTTP server binary is accessible. Alternatively, check the Oracle inventory file for OHS version entries.
    Affected if Version returned is exactly 12.2.1.4.0
  3. Verify OHS is network accessible
    Confirm the HTTP server is bound to a network interface and listening on HTTP/HTTPS ports (typically 7777, 8888, or 443/80). Check OHS configuration files (httpd.conf or ohstype.conf) for 'Listen' directives and 'ServerName' settings.
    Affected if OHS is exposed to network access via HTTP and responds to requests

The environment is affected only if Oracle HTTP Server version 12.2.1.4.0 is installed and network-accessible via HTTP, as this specific version contains the information disclosure flaw in the Core component.

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 the relevant Oracle Critical Patch Update for Oracle HTTP Server 12.2.1.4.0. Until a patch is available, restrict network access to Oracle HTTP Server endpoints using firewall rules or network segmentation, and monitor for unusual read access patterns.

Recommended fix High confidence

Oracle HTTP Server 14.1.2.0.0 (14c)

  1. 1. Download Oracle HTTP Server 14.1.2.0.0 (or latest 14c version) from Oracle Technology Network
  2. 2. Review the Oracle HTTP Server 14c Installation Guide for your platform
  3. 3. Backup your current Oracle HTTP Server 12.2.1.4.0 configuration files, including opmn.xml, httpd.conf, and any custom module configurations
  4. 4. Stop all Oracle HTTP Server processes using opmnctl shutdown
  5. 5. Install Oracle HTTP Server 14.1.2.0.0 to a new Oracle home directory
  6. 6. Migrate configuration files from the old 12.2.1.4.0 Oracle home to the new 14.1.2.0.0 Oracle home, updating paths and directives as needed
  7. 7. Start the new Oracle HTTP Server instance using opmnctl startall
  8. 8. Verify the server is operational and test your applications
Caveat Oracle HTTP Server 14c has architectural changes from 12c; some directives, modules, or third-party integrations may require configuration adjustments. Review the Migration Guide before upgrading.

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

Fix this in HTTP Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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