dbcve.org
Bi PublisherApplication · Oracle

CVE-2021-2400

HIGH · 7.5 CVSS v3.1 Published 2021-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
High EPSS 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 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 unauthenticated attacker with network access via HTTP to compromise Oracle BI Publisher. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle BI Publisher accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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-2021-2400 is an easily exploitable vulnerability in Oracle BI Publisher's E-Business Suite XDO component affecting versions 5.5.0.0.0, 11.1.1.9.0, 12.2.1.3.0, and 12.2.1.4.0. The flaw allows unauthenticated remote attackers with network access via HTTP to potentially access critical or all accessible data within Oracle BI Publisher, representing a high-confidentiality impact information disclosure issue.

MitigationApply Oracle Critical Patch Updates (CPU) when available for this vulnerability; until patched, restrict network access to Oracle BI Publisher endpoints and implement Web Application Firewall (WAF) rules to detect anomalous HTTP requests.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 BI Publisher version
    Locate the BI Publisher installation directory and check the version file or WAR file version. Common locations include: check the about page in the BI Publisher web interface, or look for version info in the installation logs or registry. The version is typically displayed in the Oracle BI Publisher console under 'Help' > 'About'.
    Affected if The installed version matches exactly 5.5.0.0.0, 11.1.1.9.0, 12.2.1.3.0, or 12.2.1.4.0
  2. Confirm E-Business Suite XDO component is present
    Check if the E-Business Suite XDO component is installed and enabled within Oracle BI Publisher. This is typically found in the BI Publisher administration console under 'Components' or 'XDO' configuration settings. Look for XDO-related configuration files or modules in the BI Publisher home directory.
    Affected if The E-Business Suite XDO component is installed and configured in the BI Publisher environment
  3. Verify network accessibility of BI Publisher
    Determine if the Oracle BI Publisher web interface is exposed to network access. Check firewall rules, load balancer configurations, or reverse proxy settings that expose the BI Publisher HTTP endpoints (typically on ports 9704, 8080, or 443). Use curl or a browser to confirm the BI Publisher login page is accessible from external networks.
    Affected if BI Publisher HTTP endpoints are accessible from untrusted networks without VPN or authentication barrier

You are affected if Oracle BI Publisher is running any of the versions 5.5.0.0.0, 11.1.1.9.0, 12.2.1.3.0, or 12.2.1.4.0 with the E-Business Suite XDO component enabled and the interface is network-accessible.

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 Updates (CPU) when available for this vulnerability; until patched, restrict network access to Oracle BI Publisher endpoints and implement Web Application Firewall (WAF) rules to detect anomalous HTTP requests.

Fix this in Bi 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-2021-2400 — 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-2021-2400 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