dbcve.org
Business IntelligenceApplication · Oracle

CVE-2020-14815

HIGH · 8.2 CVSS v3.1 Published 2020-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges

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 Fusion Middleware (component: Analytics Actions). Supported versions that are affected are 5.5.0.0.0, 12.2.1.3.0 and 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated 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. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Business Intelligence Enterprise Edition accessible data as well as unauthorized update, insert or delete access to some of Oracle Business Intelligence Enterprise Edition accessible data. CVSS 3.1 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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

CVE-2020-14815 is an easily exploitable vulnerability in Oracle Business Intelligence Enterprise Edition's Analytics Actions component. It allows unauthenticated remote attackers via HTTP to gain unauthorized access to critical data or complete visibility into all OBIEE accessible data, plus unauthorized modification capabilities. The attack requires human interaction (UI:R), and while scope is changed (S:C) meaning it may impact additional products, availability impact is none.

MitigationApply the relevant Oracle Critical Patch Update for CVE-2020-14815 to affected versions 5.5.0.0.0, 12.2.1.3.0, and 12.2.1.4.0. Until patched, restrict network access to OBIEE interfaces and educate users about phishing/social engineering risks given the required human interaction.

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:= 5.5.0.0.0= 12.2.1.3.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
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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 if Oracle Business Intelligence Enterprise Edition is installed
    Search for OBIEE installation directories or check for Oracle BI services/processes running on the system. Common locations include $ORACLE_HOME/bi and related paths.
    Affected if OBIEE software is found on the system
  2. Determine the installed OBIEE version
    Check the version of Oracle Business Intelligence using opatch lsinventory, the Oracle BI Administrator tool, or look for version files in the installation directory.
    Affected if Installed version matches 5.5.0.0.0, 12.2.1.3.0, or 12.2.1.4.0
  3. Verify if Analytics Actions component is enabled and exposed
    Check the OBIEE configuration for the Analytics Actions component. This is typically managed through the Oracle BI Presentation Services configuration or the Oracle Enterprise Manager. Confirm the component is accessible via HTTP.
    Affected if Analytics Actions component is enabled and accessible over HTTP
  4. Assess network accessibility of OBIEE interfaces
    Review firewall rules, load balancer configurations, and network ACLs to determine if the OBIEE web interfaces are exposed to untrusted networks or the internet.
    Affected if OBIEE HTTP interfaces are accessible from untrusted networks without proper authentication barriers

User is affected if OBIEE with version 5.5.0.0.0, 12.2.1.3.0, or 12.2.1.4.0 is installed with the Analytics Actions component enabled and exposed over HTTP to potentially untrusted users.

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 the relevant Oracle Critical Patch Update for CVE-2020-14815 to affected versions 5.5.0.0.0, 12.2.1.3.0, and 12.2.1.4.0. Until patched, restrict network access to OBIEE interfaces and educate users about phishing/social engineering risks given the required human interaction.

Fix this in Business Intelligence Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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