# CVE-2019-2406: Privilege escalation in Oracle Database

> High-privileged attackers can compromise the Core RDBMS component of Oracle Database Server via network access, leading to full system takeover.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jan 2019
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-m656-xvfp-5f44

## What is CVE-2019-2406?

CVE-2019-2406 is a high-severity vulnerability in Oracle Database, published on 16 Jan 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in the Core RDBMS component of Oracle Database Server. Supported versions that are affected are 12.1.0.2, 12.2.0.1 and 18c. Easily exploitable vulnerability allows high privileged attacker having Create Session, Execute Catalog Role privilege with network access via Oracle Net to compromise Core RDBMS. Successful attacks of this vulnerability can result in takeover of Core RDBMS. CVSS 3.0 Base Score 7.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

## Which versions are affected by CVE-2019-2406?

It affects 1 product.


Products: Oracle Database.

## How do I fix CVE-2019-2406?

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

## Is CVE-2019-2406 being exploited?

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

## Other vulnerabilities in Oracle Database

- [CVE-2017-10202](https://insights.sbomify.com/CVE-2017-10202/): Privilege escalation in Oracle Database (critical 9.9)
- [CVE-2017-3310](https://insights.sbomify.com/CVE-2017-3310/): Privilege escalation in Oracle Database (critical 9.0)
- [CVE-2016-3609](https://insights.sbomify.com/CVE-2016-3609/): Other in n/a (critical 9.0)
- [CVE-2016-3454](https://insights.sbomify.com/CVE-2016-3454/): Other in n/a (critical 9.0)
- [CVE-2022-21510](https://insights.sbomify.com/CVE-2022-21510/): Privilege escalation in Database - Enterprise Edition (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-2406 and fix it if it is affected.

What it is: CVE-2019-2406 is a high-severity vulnerability in Oracle Database, published on 16 Jan 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-2406 in the wild and no public exploit code.

Affected product: Oracle Database. 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-2019-2406/ (Markdown: https://insights.sbomify.com/CVE-2019-2406/index.md)
```

## Sources

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

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