dbcve.org
Business Intelligence PublisherApplication · Oracle

CVE-2020-14880

HIGH · 8.5 CVSS v3.1 Published 2020-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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 BI Publisher product of Oracle Fusion Middleware (component: E-Business Suite - XDO). Supported versions that are affected are 5.5.0.0.0, 11.1.1.9.0, 12.2.1.3.0 and 12.2.1.4.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise BI Publisher. While the vulnerability is in BI Publisher, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all BI Publisher accessible data as well as unauthorized update, insert or delete access to some of BI Publisher accessible data. CVSS 3.1 Base Score 8.5 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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 · high confidence

Oracle BI Publisher contains an access control vulnerability in the XDO (E-Business Suite) component that allows low-privileged attackers to bypass authorization and gain unauthorized access to critical data or full read/write access to BI Publisher data via HTTP. The Changed scope indicates attacks may impact additional Oracle products.

MitigationApply Oracle Critical Patch Update (CPU) for October 2020 or later, which contains the security fix for this vulnerability. Restrict network access to BI Publisher administrative interfaces until patching can be completed.

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:= 5.5.0.0.0= 11.1.1.9.0= 12.2.1.3.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
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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 Oracle BI Publisher installed version
    Access the BI Publisher administration console or about page (typically at /xmlpserver/about.jsp or /xmlpadmin/about.jsp) and note the full version number displayed
    Affected if The version shown matches exactly 5.5.0.0.0, 11.1.1.9.0, 12.2.1.3.0, or 12.2.1.4.0
  2. Check installation directory version file
    Locate the version file in the BI Publisher installation directory, commonly named version.txt or manifest in the Oracle_BI1 directory or $ORACLE_HOME/xmlp/admin, and read the version string
    Affected if The version file reports any of the four affected versions listed above
  3. Verify XDO component is accessible
    Confirm the XDO servlet is exposed by attempting to access the XDO request path (such as /xmlpserver/services/XDOService or /xmlp/services/XDO) and checking if the endpoint responds
    Affected if The XDO endpoint is reachable and responds to HTTP requests, indicating the vulnerable component is active
  4. Review HTTP access to XDO servlet
    Use a web proxy or curl to send an unauthenticated or low-privilege HTTP request to the XDO servlet path and examine whether the response returns data or accepts commands without proper authorization
    Affected if Unauthenticated or low-privileged requests to the XDO endpoint return data or execute without being rejected, confirming the authorization bypass is present

If the installed Oracle BI Publisher version exactly matches 5.5.0.0.0, 11.1.1.9.0, 12.2.1.3.0, or 12.2.1.4.0 AND the XDO component is accessible, the environment is affected by this vulnerability.

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) for October 2020 or later, which contains the security fix for this vulnerability. Restrict network access to BI Publisher administrative interfaces until patching can be completed.

Fix this in Business Intelligence Publisher Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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