dbcve.org
Bi PublisherApplication · Oracle

CVE-2024-21084

MEDIUM · 5.8 CVSS v3.1 Published 2024-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
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 Analytics (component: Service Gateway). Supported versions that are affected are 7.0.0.0.0 and 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle BI Publisher. 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 read access to a subset of Oracle BI Publisher accessible data. CVSS 3.1 Base Score 5.8 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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

Oracle BI Publisher's Service Gateway component contains an information disclosure vulnerability allowing unauthenticated remote attackers to read a subset of accessible data via HTTP. The attack requires network access but no authentication, with Low confidentiality impact.

MitigationApply Oracle Critical Patch Updates for the affected versions (7.0.0.0.0 and 12.2.1.4.0) or upgrade to a patched version. If immediate patching is not possible, restrict network access to the Service Gateway component.

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:= 7.0.0.0.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
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/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 or check for the bi-publisher service/process on the system. Common paths include $ORACLE_HOME/bipublisher or check the application server (WebLogic/OC4J) deployments.
    Affected if Oracle BI Publisher is not installed on the system
  2. Check installed version
    Query the BI Publisher version through the administration console, check the About page at /xmlpserver/faces/admin/about.jspx, or examine the manifest file in the deployment directory. Compare against the affected versions: 7.0.0.0.0 or 12.2.1.4.0
    Affected if The installed version is exactly 7.0.0.0.0 or exactly 12.2.1.4.0
  3. Determine if Service Gateway is enabled
    Check the BI Publisher configuration files (xmlp-server-config.xml or similar) for the Service Gateway component settings, or query the administration console for Service Gateway status. The endpoint typically resides under /xmlpserver/services/ServiceGateway
    Affected if Service Gateway component is enabled and accessible in the configuration
  4. Verify network exposure
    Test HTTP access to the Service Gateway endpoint (such as /xmlpserver/services/ServiceGateway) from an unauthenticated perspective. Check firewall rules and reverse proxy configurations that allow external access to the BI Publisher web paths.
    Affected if The Service Gateway endpoint is reachable over the network without authentication

The environment is affected only if Oracle BI Publisher version 7.0.0.0.0 or 12.2.1.4.0 is installed AND the Service Gateway component is enabled and network-accessible without authentication.

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 for the affected versions (7.0.0.0.0 and 12.2.1.4.0) or upgrade to a patched version. If immediate patching is not possible, restrict network access to the Service Gateway component.

Fix this in Bi Publisher Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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