CVE-2021-2003
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 Business Intelligence Enterprise Edition product of Oracle Fusion Middleware (component: Analytics Web Dashboards). Supported versions that are affected are 5.5.0.0.0, 11.1.1.9.0, 12.2.1.3.0 and 12.2.1.4.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Business Intelligence Enterprise Edition. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Business Intelligence Enterprise Edition, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Business Intelligence Enterprise Edition accessible data as well as unauthorized read access to a subset of 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 confidenceA vulnerability in Oracle Fusion Middleware Business Intelligence Enterprise Edition's Analytics Web Dashboards allows low-privileged attackers with network access via HTTP to achieve unauthorized read and write (update/insert/delete) access to a subset of accessible data. The attack requires human interaction and may impact 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= 5.5.0.0.0= 11.1.1.9.0= 12.2.1.3.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 versionCheck the Oracle BI version through Enterprise Manager (Fusion Middleware Control), the Oracle BI Administration Tool, or examine the ORACLE_HOME/oracle_common/modules/oracle.bi.ee directory for version.info. On the system console, navigate to the BI Domain > bifoundation > coreapplication > About Oracle Business Intelligence.Affected if installed version equals 5.5.0.0.0, 11.1.1.9.0, 12.2.1.3.0, or 12.2.1.4.0
-
Confirm Analytics Web Dashboards component is runningIn Oracle Enterprise Manager (Fusion Middleware Control), navigate to coreapplication > Capacity > Components, or check the Oracle BI Server status via opmnctl process. The Analytics Web Dashboards is part of the coreapplication deployment.Affected if Analytics Web Dashboards component is deployed and running as part of the Oracle Business Intelligence installation
-
Verify network accessibility of HTTP servicesCheck if the Oracle BI Presentation Server (commonly on port 9502, 9704, or 443/8080) is exposed to the network. Review load balancer configurations, web server plugins, and firewall rules that expose the analytics URLs (/analytics/) to untrusted networks.Affected if Analytics Web Dashboards HTTP endpoint is accessible from network locations beyond trusted administrators
-
Review for anomalous data access patternsExamine Oracle BI audit logs and access logs (located in $ORACLE_HOME/instances/instance1/diagnostics/logs/OracleBIAudit) and the BI Publisher audit repository for unexpected read or write operations performed by low-privilege users.Affected if audit logs show data access or modification by users who should not have such permissions to the affected data subsets
A user is affected if their Oracle Business Intelligence installation runs version 5.5.0.0.0, 11.1.1.9.0, 12.2.1.3.0, or 12.2.1.4.0 AND the Analytics Web Dashboards component is network-accessible via HTTP.
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 Critical Patch Update (CPU) for January 2021 or later to obtain the security fix for this vulnerability in the Analytics Web Dashboards component.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-2003 — 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-2021-2003 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