dbcve.org
Bi PublisherApplication · Oracle

CVE-2024-21083

HIGH · 7.2 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 →
78/100
Remediation priority · High
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 Oracle BI Publisher product of Oracle Analytics (component: Script Engine). Supported versions that are affected are 7.0.0.0.0 and 12.2.1.4.0. Easily exploitable vulnerability allows high privileged attacker with network access via HTTP to compromise Oracle BI Publisher. Successful attacks of this vulnerability can result in takeover of Oracle BI Publisher. CVSS 3.1 Base Score 7.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

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's Script Engine allows a high-privileged attacker with network access via HTTP to execute arbitrary code and take over the BI Publisher instance. The attack requires high privileges (PR:H) but no user interaction (UI:N), and results in full compromise of confidentiality, integrity, and availability.

MitigationApply Oracle Critical Patch Update (CPU) containing the fix for CVE-2024-21083 to affected versions 7.0.0.0.0 and 12.2.1.4.0. Until patch is applied, restrict network access to BI Publisher and limit Script Engine permissions to highly trusted administrators 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:= 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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. Confirm Oracle BI Publisher installation
    Locate the BI Publisher deployment in your environment. Common installation paths include Oracle WebLogic Server domains, Oracle Fusion Middleware home, or check the Oracle Enterprise Manager for BI Publisher components.
    Affected if Oracle BI Publisher software is present in the environment
  2. Identify installed BI Publisher version
    Access the BI Publisher Administration page (typically at /xmlp/admin) or use Oracle Enterprise Manager to view the exact version number. Compare against the affected versions 7.0.0.0.0 and 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. Verify Script Engine is enabled
    Access BI Publisher Administration console and check the Script Engine configuration settings. This feature allows execution of scripts within BI Publisher and is the vulnerable component.
    Affected if Script Engine feature is enabled in the BI Publisher configuration
  4. Check network accessibility of BI Publisher
    Determine if the BI Publisher HTTP endpoints are accessible from network segments outside the trusted admin network. Verify HTTP listener status and firewall rules.
    Affected if BI Publisher HTTP ports are exposed to untrusted network access

You are affected if Oracle BI Publisher versions 7.0.0.0.0 or 12.2.1.4.0 are installed, the Script Engine feature is enabled, and the HTTP interface is network-accessible to the attacker.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) containing the fix for CVE-2024-21083 to affected versions 7.0.0.0.0 and 12.2.1.4.0. Until patch is applied, restrict network access to BI Publisher and limit Script Engine permissions to highly trusted administrators only.

Recommended fix Moderate confidence

Oracle BI Publisher 12.2.1.4.0 + January 2024 CPU (or later) / Oracle Analytics Cloud latest supported version

  1. 1. Identify the current Oracle BI Publisher version in use (7.0.0.0.0 or 12.2.1.4.0)
  2. 2. Access Oracle Support portal (support.oracle.com) and search for CVE-2024-21083
  3. 3. Download and apply the relevant security patch for your version. For 12.2.1.4.0, apply the January 2024 Critical Patch Update (or subsequent updates containing the fix)
  4. 4. For version 7.0.0.0.0, upgrade to the latest supported Oracle Analytics Cloud (OAC) or on-premises BI Publisher version
  5. 5. After applying the patch/upgrade, verify the Script Engine component is functioning correctly
  6. 6. Confirm the version now includes the security fix for CVE-2024-21083
Caveat Review Oracle upgrade documentation for changes between versions; test thoroughly in non-production environment before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bi Publisher Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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