# CVE-2017-10292: Privilege escalation in Oracle Database

> High-privileged attackers can modify RDBMS Security data in Oracle Database Server, requiring local access and specific privileges.

- **Severity:** Low 2.3 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 19 Oct 2017
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-36qq-p346-g8r2

## What is CVE-2017-10292?

CVE-2017-10292 is a low-severity vulnerability in Oracle Database, published on 19 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the RDBMS Security component of Oracle Database Server. Supported versions that are affected are 11.2.0.4, 12.1.0.2 and 12.2.0.1. Easily exploitable vulnerability allows high privileged attacker having Create User privilege with logon to the infrastructure where RDBMS Security executes to compromise RDBMS Security. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of RDBMS Security accessible data. CVSS 3.0 Base Score 2.3 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N).

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2017-10292?

It affects 1 product.


Products: Oracle Database.

## How do I fix CVE-2017-10292?

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

## Is CVE-2017-10292 being exploited?

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

What it is: CVE-2017-10292 is a low-severity vulnerability in Oracle Database, published on 19 Oct 2017. 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-2017-10292 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-2017-10292/ (Markdown: https://insights.sbomify.com/CVE-2017-10292/index.md)
```

## Sources

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

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