# CVE-2024-20916: Missing authorization in Enterprise Manager Base Platform

> High-privileged attackers on the local network can modify or read critical data and cause partial denial of service in Oracle Enterprise Manager.

- **Severity:** High 8.3 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2024
- **Updated:** 20 Jun 2025
- **Also known as:** GHSA-3x82-g63q-53gm

## What is CVE-2024-20916?

CVE-2024-20916 is a high-severity missing authorization vulnerability in Oracle Corporation Enterprise Manager Base Platform, published on 16 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the Oracle Enterprise Manager Base Platform product of Oracle Enterprise Manager (component: Event Management).   The supported version that is affected is 13.5.0.0. Easily exploitable vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the Oracle Enterprise Manager Base Platform executes to compromise Oracle Enterprise Manager Base Platform.  While the vulnerability is in Oracle Enterprise Manager Base Platform, attacks may significantly impact additional products (scope change).  Successful attacks of this vulnerability can result in  unauthorized creation, deletion or modification access to critical data or all Oracle Enterprise Manager Base Platform accessible data as well as  unauthorized access to critical data or complete access to all Oracle Enterprise Manager Base Platform accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Enterprise Manager Base Platform. CVSS 3.1 Base Score 8.3 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-20916?

It affects 1 product.


Products: Oracle Enterprise Manager.

## How do I fix CVE-2024-20916?

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

## Is CVE-2024-20916 being exploited?

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

## Other vulnerabilities in Oracle Corporation Enterprise Manager Base Platform

- [CVE-2007-2129](https://insights.sbomify.com/CVE-2007-2129/): Other in n/a (critical 10.0)
- [CVE-2006-3721](https://insights.sbomify.com/CVE-2006-3721/): Other in n/a (critical 10.0)
- [CVE-2006-1885](https://insights.sbomify.com/CVE-2006-1885/): Other in n/a (critical 10.0)
- [CVE-2019-2895](https://insights.sbomify.com/CVE-2019-2895/): Auth bypass in Enterprise Manager for Exadata (high 7.5)
- [CVE-2007-0292](https://insights.sbomify.com/CVE-2007-0292/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-20916 and fix it if it is affected.

What it is: CVE-2024-20916 is a high-severity missing authorization vulnerability in Oracle Corporation Enterprise Manager Base Platform, published on 16 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-20916 in the wild and no public exploit code.

Affected product: Oracle Corporation Enterprise Manager Base Platform. 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-2024-20916/ (Markdown: https://insights.sbomify.com/CVE-2024-20916/index.md)
```

## Sources

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

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