dbcve.org
Bi PublisherApplication · Oracle

CVE-2024-21254

HIGH · 8.8 CVSS v3.1 Published 2024-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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: Web Server). Supported versions that are affected are 7.0.0.0.0, 7.6.0.0.0 and 12.2.1.4.0. Easily exploitable vulnerability allows low privileged 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 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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

Vulnerability in Oracle BI Publisher's Web Server component allows a low-privileged attacker with network access via HTTP to completely compromise the system, achieving full takeover with high impact on confidentiality, integrity, and availability.

MitigationApply the relevant Oracle security patch for Oracle BI Publisher (Oracle Analytics) to address this vulnerability in the Web Server component.

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= 7.6.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm Oracle BI Publisher installation
    Locate the BI Publisher installation directory or check for the Oracle BI Publisher web application running on your application server (commonly on ports 9500, 9704, or 8080). Access the application login page or administration console to verify the product is present.
    Affected if Oracle BI Publisher web application is not installed or accessible in your environment.
  2. Identify installed BI Publisher version
    Access the BI Publisher 'About' page, typically found at /xmlpserver/faces/about.jsp or check the version file in the installation directory (such as VERSION.txt or the Oracle_BI1 directory). Alternatively, check the Oracle Enterprise Manager or Oracle Fusion Middleware Control for the deployed BI Publisher version.
    Affected if You cannot determine the version - further investigation needed.
  3. Compare version against affected releases
    Verify if your installed version matches exactly 7.0.0.0.0, 7.6.0.0.0, or 12.2.1.4.0. Note that only these exact versions are affected according to the advisory.
    Affected if Your installed version is one of the three affected versions: 7.0.0.0.0, 7.6.0.0.0, or 12.2.1.4.0.
  4. Confirm Web Server component is network-accessible
    Check if the BI Publisher Web Server component (xmlpserver) is accessible over HTTP/HTTPS from the network. Test connectivity to the application URL (commonly /xmlpserver or /bidata).
    Affected if The Web Server component is exposed to network access and your version matches an affected release.

You are affected if Oracle BI Publisher is installed with version exactly 7.0.0.0.0, 7.6.0.0.0, or 12.2.1.4.0 and the Web Server component is network-accessible 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 relevant Oracle security patch for Oracle BI Publisher (Oracle Analytics) to address this vulnerability in the Web Server component.

Fix this in Bi Publisher Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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