dbcve.org
Business IntelligenceApplication · Oracle

CVE-2024-21001

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
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 Business Intelligence Enterprise Edition product of Oracle Analytics (component: BI Platform Security). The supported version that is affected is 7.0.0.0.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Business Intelligence Enterprise Edition. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Business Intelligence Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Business Intelligence Enterprise Edition accessible data as well as unauthorized read access to a subset of Oracle Business Intelligence Enterprise Edition accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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

Access control vulnerability in Oracle Business Intelligence Enterprise Edition 7.0.0.0.0 BI Platform Security component allowing low-privileged attackers with network access via HTTP to achieve unauthorized read and write access to subset of accessible data. Exploitation requires human interaction and results in scope change affecting additional products.

MitigationApply Oracle Critical Patch Update (CPU) containing the CVE-2024-21001 fix. Until patched, restrict HTTP access to OBIEE and implement additional request validation/monitoring.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 BIEE installation and version
    Check the installed Oracle Business Intelligence Enterprise Edition version by examining the system information, ORACLE_BI_HOME directory, or using the Oracle BI Administration Tool. Common paths include $ORACLE_BI_HOME/systems/NQServer/ or check the NQServer.log startup banner for version information.
    Affected if The installed version is exactly 7.0.0.0.0 (this is the sole affected version per the CVE)
  2. Confirm BI Platform Security component is in use
    Determine if the BI Platform Security component is enabled. This component handles authentication and authorization for OBIEE. Check the Oracle BI configuration files (NQSConfig.INI, NQClusterConfig.INI) in the $ORACLE_BI_HOME/config/NQServer directory for security-related settings.
    Affected if BI Platform Security component is configured and handling authentication for the OBIEE installation
  3. Verify HTTP network accessibility
    Check if the Oracle BI Presentation Services (obips) and Oracle BI Server (obis) are exposed over HTTP/HTTPS to network-accessible interfaces. Review web server configuration (Oracle HTTP Server, OHS, or embedded web logic) and firewall rules. Look for exposed ports (typically 9500, 9704, 9502 for Presentation Services).
    Affected if HTTP access to OBIEE is exposed to untrusted networks (internet or users outside the security perimeter)
  4. Check for presence of CPU patch
    Query the Oracle BI patch inventory. On Linux/Unix, review $ORACLE_BI_HOME/oracle_common/modules or use 'opatch lsinventory' command. On Windows, check the Oracle Inventory (typically in C:\Program Files\Oracle\Inventory). Look for patches applied after the January 2024 CPU.
    Affected if No Oracle Critical Patch Update containing the CVE-2024-21001 fix has been applied (patch absent from inventory)

The environment is affected if Oracle Business Intelligence Enterprise Edition version 7.0.0.0.0 is installed with BI Platform Security enabled and HTTP network access is exposed, and the CVE fix patch has not been applied.

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 (CPU) containing the CVE-2024-21001 fix. Until patched, restrict HTTP access to OBIEE and implement additional request validation/monitoring.

Fix this in Business Intelligence Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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