# CVE-2016-3454: Other in n/a

> Remote attackers can compromise confidentiality, integrity, and availability of Oracle Database Server via unspecified vectors in the Java VM component.

- **Severity:** Critical 9.0 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2016
- **Updated:** 15 Oct 2024
- **Also known as:** GHSA-w5qf-223h-277f

## What is CVE-2016-3454?

CVE-2016-3454 is a critical vulnerability in Oracle Database, published on 21 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in the Java VM component in Oracle Database Server 11.2.0.4, 12.1.0.1, and 12.1.0.2 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors.

## Which versions are affected by CVE-2016-3454?

It affects 1 product.


Products: Oracle Database.

## How do I fix CVE-2016-3454?

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

## Is CVE-2016-3454 being exploited?

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

What it is: CVE-2016-3454 is a critical vulnerability in Oracle Database, published on 21 Apr 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-3454 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-2016-3454/ (Markdown: https://insights.sbomify.com/CVE-2016-3454/index.md)
```

## Sources

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

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