Skip to main content
CISA Known Exploited Vulnerabilities

Oracle Business Intelligence Enterprise Edition Path Transversal is confirmed as actively exploited and is listed in the CISA KEV catalog.

Added to KEV
2022-01-18
Remediation due
2022-07-18

Required action
Apply updates per vendor instructions.

CISA notes
https://nvd.nist.gov/vuln/detail/CVE-2020-14864

Description

Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Fusion Middleware (component: Installation). 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 of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Business Intelligence Enterprise Edition accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Key Findings

as of 2026-11-22
All KEV statistics→
  • CISA added CVE-2020-14864 to the KEV catalog 454 days after its CVE record was published.
  • It is one of 46 Oracle entries in the CISA KEV catalog, and one of 22 added in 2022.
  • Its current EPSS score (97.2%) is higher than that of 82% of CISA KEV entries.

Severity

CVSS 3.1 · CNA · Base score7.5 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NOpen in CVSS calculator
SSVC · CISA-ADP
Exploitationactive
Automatableyes
Technical impactpartial

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
3 days
Asset not publicly exposed
14 days
KEV due date
2022-07-18
181 days after listing

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable yes, technical impact partial, 2024-09-26).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet.

CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.

Affected Products

ProductAffected versions
Oracle Corporation
Business Intelligence Enterprise Edition
5.5.0.0.0
12.2.1.3.0
12.2.1.4.0

More from Oracle

All Oracle CVEs→

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.