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

> Low-privileged attackers can compromise the OJVM component of Oracle Database Server, leading to full takeover of the component.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jan 2017
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-h788-pcwr-mwqf

## What is CVE-2017-3310?

CVE-2017-3310 is a critical vulnerability in Oracle Database, published on 27 Jan 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Vulnerability in the OJVM component of Oracle Database Server. Supported versions that are affected are 11.2.0.4 and 12.1.0.2. Easily exploitable vulnerability allows low privileged attacker having Create Session, Create Procedure privilege with network access via multiple protocols to compromise OJVM. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in OJVM, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of OJVM. CVSS v3.0 Base Score 9.0 (Confidentiality, Integrity and Availability impacts).

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

It affects 1 product.


Products: Oracle Database.

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

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

## Is CVE-2017-3310 being exploited?

There is no known exploitation of CVE-2017-3310 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-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)
- [CVE-2017-10321](https://insights.sbomify.com/CVE-2017-10321/): Privilege escalation in Oracle Database (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3310 and fix it if it is affected.

What it is: CVE-2017-3310 is a critical vulnerability in Oracle Database, published on 27 Jan 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-3310 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-3310/ (Markdown: https://insights.sbomify.com/CVE-2017-3310/index.md)
```

## Sources

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

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