dbcve.org
Business Intelligence PublisherApplication · Oracle

CVE-2021-2062

HIGH · 7.6 CVSS v3.1 Published 2021-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 Fusion Middleware (component: Web Server). 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 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. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle BI Publisher accessible data as well as unauthorized update, insert or delete access to some of Oracle BI Publisher accessible data. CVSS 3.1 Base Score 7.6 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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

Vulnerability in Oracle BI Publisher Web Server component allowing low-privileged attackers with network access via HTTP to compromise the system. Requires human interaction to exploit. Successful attacks enable unauthorized access to critical or all accessible data, plus unauthorized update, insert or delete operations on some data. Likely involves injection-based attack vector given confidentiality (high) and integrity (low) impacts.

MitigationApply Oracle Critical Patch Update for CVE-2021-2062. Until patched, restrict network access to Oracle BI Publisher and enforce least-privilege user accounts.

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
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 installation and version
    Locate the Oracle BI Publisher installation directory and check the version manifest or About page. Common paths include the Oracle BI_HOME directory or the WebLogic domain home. The version can also be retrieved via the WebLogic Administration Console or by accessing the BI Publisher diagnostic page.
    Affected if The installed version equals 5.5.0.0.0, 11.1.1.9.0, 12.2.1.3.0, or 12.2.1.4.0
  2. Confirm Web Server component is accessible
    Verify that the BI Publisher web interface is accessible by attempting to reach the HTTP endpoint (commonly on ports 7001, 9500, or 9704). Check the Oracle WebLogic Server configuration for the BI Publisher managed server.
    Affected if The web server component is running and reachable via HTTP on the network
  3. Check network exposure of the web interface
    Review firewall rules, load balancer configurations, or WebLogic network channels to determine if the BI Publisher web interface is exposed to untrusted networks. Inspect the listen-address configuration in the WebLogic Server settings.
    Affected if The HTTP interface is accessible from network segments outside the trusted internal network, making it exploitable by remote attackers
  4. Assess whether default or low-privilege accounts exist
    Review the Oracle BI Publisher user repository or integrated LDAP/SSO configuration to confirm if low-privileged user accounts exist. Check the application security configuration for assigned roles.
    Affected if Low-privileged user accounts are provisioned in the system, as the CVE specifically targets low-privileged attackers

You are affected if Oracle BI Publisher version 5.5.0.0.0, 11.1.1.9.0, 12.2.1.3.0, or 12.2.1.4.0 is installed and the web server is network-accessible to potential attackers.

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-2021-2062. Until patched, restrict network access to Oracle BI Publisher and enforce least-privilege user accounts.

Fix this in Business Intelligence Publisher Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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