dbcve.org
Business Intelligence PublisherApplication · Oracle

CVE-2024-20980

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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 6.4.0.0.0 and 7.0.0.0.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle BI Publisher. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle BI Publisher, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle BI Publisher accessible data as well as unauthorized read access to a subset of Oracle BI Publisher accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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

Vulnerability in the Web Server component of Oracle BI Publisher (versions 6.4.0.0.0 and 7.0.0.0.0) allows low-privileged attackers with network access via HTTP to achieve unauthorized read, insert, update, and delete access to a subset of accessible data. Exploitation requires human interaction and results in a scope change affecting additional products beyond BI Publisher.

MitigationApply Oracle Critical Patch Update for CVE-2024-20980 when available. In the interim, restrict network access to Oracle BI Publisher HTTP endpoints and educate users about social engineering risks given the required user interaction.

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
Business Intelligence PublisherApplication
Affected:= 6.4.0.0.0= 7.0.0.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
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 if Oracle BI Publisher is installed
    Check for BI Publisher installation directories or look for 'Oracle BI Publisher' or 'XMLP' processes running on the system. Common installation paths include $ORACLE_HOME/bipublisher or similar. On Windows, check Program Files for Oracle BI Publisher.
    Affected if Oracle BI Publisher software is present on the system
  2. Verify the installed BI Publisher version
    Locate the version file or check the about page in the BI Publisher web interface. The version is typically displayed in the administration console or in the product's Readme/About section. Compare the version number to 6.4.0.0.0 or 7.0.0.0.0.
    Affected if The installed version matches exactly 6.4.0.0.0 or 7.0.0.0.0
  3. Confirm the Web Server component is enabled and accessible
    Check if the BI Publisher HTTP listener or web application is running and accessible. This is typically exposed on ports like 9704, 8080, or 443 depending on configuration. Verify the web service endpoints respond to HTTP requests.
    Affected if The Web Server component is running and accessible via HTTP(s) on any port
  4. Assess network exposure of BI Publisher HTTP endpoints
    Review firewall rules, load balancer configurations, or reverse proxy settings to determine if BI Publisher HTTP endpoints are reachable from untrusted networks. Check if the endpoints are exposed to the public internet or only to trusted internal networks.
    Affected if BI Publisher HTTP endpoints are accessible from untrusted or external networks without proper access controls

A user is affected if they have Oracle BI Publisher version 6.4.0.0.0 or 7.0.0.0.0 running with the Web Server component exposed to network access, regardless of privilege level, given that exploitation requires human interaction.

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 for CVE-2024-20980 when available. In the interim, restrict network access to Oracle BI Publisher HTTP endpoints and educate users about social engineering risks given the required user interaction.

Fix this in Business Intelligence Publisher Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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