# CVE-2020-14609: Missing authorization in Oracle Business Intelligence Enterprise Edition

> Unauthenticated attackers can access critical data, modify some data, and cause partial denial of service in Oracle Business Intelligence Enterprise Edition.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2020
- **Updated:** 27 Sep 2024
- **Also known as:** GHSA-fwh4-xh88-xxmp

## What is CVE-2020-14609?

CVE-2020-14609 is a high-severity missing authorization vulnerability in Oracle Business Intelligence, published on 15 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Oracle Business Intelligence Enterprise Edition product of Oracle Fusion Middleware (component: Analytics Web Answers). 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 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 as well as unauthorized update, insert or delete access to some of Oracle Business Intelligence Enterprise Edition accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Business Intelligence Enterprise Edition. CVSS 3.1 Base Score 8.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L).

## Which versions are affected by CVE-2020-14609?

It affects 1 product.


Products: Oracle Business Intelligence.

## How do I fix CVE-2020-14609?

No fix has been published for CVE-2020-14609 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-14609 being exploited?

There is no known exploitation of CVE-2020-14609 in the wild and no public exploit code.

## Other vulnerabilities in Oracle Business Intelligence

- [CVE-2020-14864](https://insights.sbomify.com/CVE-2020-14864/): Oracle Business Intelligence Enterprise Edition Path Transversal (high 7.5, exploited in the wild)
- [CVE-2021-2456](https://insights.sbomify.com/CVE-2021-2456/): Auth bypass in Business Intelligence Enterprise Edition (critical 9.8)
- [CVE-2020-2950](https://insights.sbomify.com/CVE-2020-2950/): Auth bypass in Oracle Business Intelligence Enterprise Edition (critical 9.8)
- [CVE-2026-71055](https://insights.sbomify.com/CVE-2026-71055/): Auth bypass in Oracle Business Intelligence Enterprise Edition (high 8.8)
- [CVE-2026-60671](https://insights.sbomify.com/CVE-2026-60671/): Missing authorization in Oracle Business Intelligence Enterprise Edition (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14609 and fix it if it is affected.

What it is: CVE-2020-14609 is a high-severity missing authorization vulnerability in Oracle Business Intelligence, published on 15 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14609 in the wild and no public exploit code.

Affected product: Oracle Business Intelligence. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-14609/ (Markdown: https://insights.sbomify.com/CVE-2020-14609/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-14609
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-14609
- OSV: https://osv.dev/vulnerability/CVE-2020-14609

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-14609/
Summaries are generated and may contain mistakes; the official description above is the record.