CVE-2024-21139
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 · uneditedVulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Analytics (component: Analytics Web Answers). Supported versions that are affected are 7.0.0.0.0, 7.6.0.0.0 and 12.2.1.4.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 · moderate confidenceVulnerability in Oracle Business Intelligence Enterprise Edition's Analytics Web Answers component allows low-privileged attackers with network access to perform unauthorized read, insert, update, and delete operations on a subset of accessible data. The attack requires human interaction and exploits the web interface to bypass access controls, potentially impacting additional products due to scope change.
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= 7.0.0.0.0= 7.6.0.0.0= 12.2.1.4.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle Business Intelligence installationLocate the Oracle BI installation directory (commonly under $ORACLE_HOME/bi) and check for the existence of the Analytics Web Answers component. On Linux/Unix, check /opt/oracle/bi/ or the configured ORACLE_HOME path. On Windows, check C:\Oracle\bi\ or the configured installation path.Affected if Oracle Business Intelligence Enterprise Edition is installed and the Analytics Web Answers component (often in the /analytics path or similar web endpoints) is present on the system.
-
Determine the installed BI versionCheck the Oracle BI version by examining the metadata or version files. Common locations include: the Oracle BI Administration Tool help > about, the opmnctl status output, or the BIEE's version file in the installation directory. Run: cd $ORACLE_HOME/bi/bin then ./opmnctl status - verbose, or check the Oracle Business Intelligence's Readme/Version file.Affected if The installed version matches 7.0.0.0.0, 7.6.0.0.0, or 12.2.1.4.0 exactly.
-
Verify Analytics Web Answers web interface accessibilityDetermine if the Analytics Web Answers web interface is accessible by checking the Oracle BI web application configuration. Examine the web server configuration (OHS/Oracle HTTP Server or embedded web logic) for the /analytics or /saw.dll endpoints. Check if the application is mapped and active in the WebLogic console or OHS configuration files.Affected if The Analytics Web Answers component is deployed and accessible via HTTP/HTTPS network endpoints.
-
Assess network exposure of the Analytics interfaceReview firewall rules, load balancer configurations, and web server access control lists (ACLs) to determine if the Analytics Web Answers URL is exposed to untrusted networks. Check if the port (typically 7001, 9500, or 80/443) is listening on external interfaces versus localhost only. Use netstat or equivalent: netstat -an | grep -E '7001|9500|80|443'.Affected if The Analytics Web Answers interface is reachable from network segments that include untrusted or public-facing IP addresses.
-
Review user privilege configurationExamine the Oracle BI repository (RPD file) and web catalog security settings to identify the current privilege assignments. Check if low-privileged users (non-admin accounts) have access to Answers functionality. In the BI Administration tool, verify the permissions on 'Answers' and 'Delivers' folders in the repository.Affected if Low-privileged (non-administrator) user accounts have access to the Analytics Web Answers functionality.
You are affected if Oracle Business Intelligence with Analytics Web Answers is installed at version 7.0.0.0.0, 7.6.0.0.0, or 12.2.1.4.0 AND the web interface is network-accessible to low-privileged users.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle's security patch for this vulnerability. Until patched, restrict network access to Analytics Web Answers and monitor for anomalous query patterns or unauthorized data access attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-21139 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21139 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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