dbcve.org
Bi PublisherApplication · Oracle

CVE-2024-21082

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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 BI Publisher product of Oracle Analytics (component: XML Services). Supported versions that are affected are 7.0.0.0.0 and 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle BI Publisher. Successful attacks of this vulnerability can result in takeover of Oracle BI Publisher. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/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 confidence

Critical unauthenticated remote code execution vulnerability in Oracle BI Publisher's XML Services component. The flaw allows any remote attacker with HTTP network access to potentially take complete control of the affected BI Publisher instance without any credentials, impacting confidentiality, integrity, and availability.

MitigationApply Oracle Critical Patch Update (CPU) containing the CVE-2024-21082 fix for affected versions 7.0.0.0.0 and 12.2.1.4.0 immediately; if patching is not immediately feasible, restrict network access to XML Services endpoints or disable the service until the patch can be applied.

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
Bi PublisherApplication
Affected:= 7.0.0.0.0= 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Oracle BI Publisher is installed
    Search for Oracle BI Publisher installation directories or check for bi-publisher related services/processes on the system. Common locations include $ORACLE_HOME/bi_publisher or similar. Check for WebLogic domains hosting BI Publisher applications.
    Affected if Oracle BI Publisher software is found on the system
  2. Determine the installed BI Publisher version
    Locate the version file or check the BI Publisher administration console for the exact version number. In WebLogic deployments, this is typically visible in the deployment manifest or console. Compare against the affected versions 7.0.0.0.0 and 12.2.1.4.0.
    Affected if Installed version matches exactly 7.0.0.0.0 or 12.2.1.4.0
  3. Check if XML Services component is enabled
    Access the BI Publisher administration interface and navigate to the XML Services configuration. In WebLogic, check the deployed bi-publisher application for XML Services module availability. Look for endpoints under /xmlpserver/services/ or similar XML service paths.
    Affected if XML Services component is exposed and accessible in the BI Publisher deployment
  4. Verify network accessibility of XML Services endpoints
    Test HTTP access to common XML Services paths such as /xmlpserver/services/ or endpoints containing 'XML' or 'XMLService' in the URL. Use curl or a browser from an external network location to determine if these endpoints respond without authentication.
    Affected if XML Services endpoints are reachable over HTTP/HTTPS from untrusted networks without requiring credentials

A system is affected if it runs Oracle BI Publisher version 7.0.0.0.0 or 12.2.1.4.0 with XML Services component enabled and accessible over the network.

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 Oracle Critical Patch Update (CPU) containing the CVE-2024-21082 fix for affected versions 7.0.0.0.0 and 12.2.1.4.0 immediately; if patching is not immediately feasible, restrict network access to XML Services endpoints or disable the service until the patch can be applied.

Fix this in Bi Publisher Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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