dbcve.org
Bi PublisherApplication · Oracle

CVE-2022-21346

HIGH · 7.5 CVSS v3.1 Published 2022-01-19
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
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: BI Publisher Security). Supported versions that are affected are 5.5.0.0.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 · high confidence

Unauthenticated remote vulnerability in Oracle BI Publisher's security component allows attackers with network access via HTTP to gain unauthorized read access to sensitive data. The flaw is easily exploitable and affects specific versions (5.5.0.0.0, 12.2.1.3.0, 12.2.1.4.0) of the middleware product.

MitigationApply Oracle Critical Patch Updates containing the fix for CVE-2022-21346. If patches are unavailable, restrict network access to BI Publisher endpoints to trusted sources only.

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= 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 installation
    Locate the Oracle BI Publisher installation directory. Common paths include $ORACLE_HOME/bi/bipublisher or check for 'bipublisher' in the installation directory. Verify the product name matches 'Oracle BI Publisher' or 'Oracle Business Intelligence Publisher'.
    Affected if Oracle BI Publisher is not installed on the system
  2. Determine installed BI Publisher version
    Check the version file in the installation directory. Typical locations include: VERSION.txt, about.html, or the Readme file in the bipublisher directory. Alternatively, access the BI Publisher login page and check any version information displayed, or query the Oracle Enterprise Manager if deployed.
    Affected if The installed version cannot be determined or BI Publisher is not present
  3. Compare version against affected releases
    Match your installed version exactly to: 5.5.0.0.0, 12.2.1.3.0, or 12.2.1.4.0. Note that this vulnerability affects these specific exact versions only, not a range.
    Affected if Installed version is exactly 5.5.0.0.0 OR 12.2.1.3.0 OR 12.2.1.4.0
  4. Verify network accessibility of BI Publisher
    Confirm that BI Publisher HTTP/HTTPS endpoints are reachable from untrusted networks. Check firewall rules, load balancer configurations, and Oracle WebLogic server network channels. Test connectivity by attempting to reach the BI Publisher URL from an external system.
    Affected if BI Publisher is exposed to untrusted network access via HTTP/HTTPS

You are affected if your Oracle BI Publisher is exactly version 5.5.0.0.0, 12.2.1.3.0, or 12.2.1.4.0 AND is accessible over the network to untrusted users.

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 containing the fix for CVE-2022-21346. If patches are unavailable, restrict network access to BI Publisher endpoints to trusted sources only.

Fix this in Bi 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-2022-21346 — 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-2022-21346 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