# CVE-2022-21410: Privilege escalation in Database - Enterprise Edition

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

- **Severity:** High 7.2 (`CVSS:3.1/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:** 19 Apr 2022
- **Updated:** 24 Sep 2024
- **Also known as:** GHSA-593w-xw98-2hpv

## What is CVE-2022-21410?

CVE-2022-21410 is a high-severity vulnerability in Oracle Database, published on 19 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Vulnerability in the Oracle Database - Enterprise Edition Sharding component of Oracle Database Server. The supported version that is affected is 19c. Easily exploitable vulnerability allows high privileged attacker having Create Any Procedure privilege with network access via Oracle Net to compromise Oracle Database - Enterprise Edition Sharding. Successful attacks of this vulnerability can result in takeover of Oracle Database - Enterprise Edition Sharding. CVSS 3.1 Base Score 7.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H).

## Which versions are affected by CVE-2022-21410?

It affects 1 product.


Products: Oracle Database.

## How do I fix CVE-2022-21410?

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

## Is CVE-2022-21410 being exploited?

There is no known exploitation of CVE-2022-21410 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-2022-21410 and fix it if it is affected.

What it is: CVE-2022-21410 is a high-severity vulnerability in Oracle Database, published on 19 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-21410 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-2022-21410/ (Markdown: https://insights.sbomify.com/CVE-2022-21410/index.md)
```

## Sources

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

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