# CVE-2019-2699: Code injection in Java

> An unauthenticated attacker can compromise Java SE via network access, leading to full takeover of the Java environment.

- **Severity:** Critical 9.0 (`CVSS:3.1/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:** 23 Apr 2019
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-xwm4-mmfg-2v6c, MINI-hgq4-jmgr-h6r7

## What is CVE-2019-2699?

CVE-2019-2699 is a critical code injection vulnerability in Oracle Jdk, published on 23 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability in the Java SE component of Oracle Java SE (subcomponent: Windows DLL). The supported version that is affected is Java SE: 8u202. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. While the vulnerability is in Java SE, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Java SE. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets (in Java SE 8), that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability can also be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. CVSS 3.0 Base Score 9.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H).

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

It affects 2 products.


Products: Oracle Jdk, Oracle Jre.

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

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

## Is CVE-2019-2699 being exploited?

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

## Other vulnerabilities in Oracle Jdk

- [CVE-2012-4681](https://insights.sbomify.com/CVE-2012-4681/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2012-1723](https://insights.sbomify.com/CVE-2012-1723/): Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-4805](https://insights.sbomify.com/CVE-2015-4805/): Deserialization in n/a (critical 10.0)
- [CVE-2015-4835](https://insights.sbomify.com/CVE-2015-4835/): Other in n/a (critical 10.0)
- [CVE-2015-4843](https://insights.sbomify.com/CVE-2015-4843/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-2699 is a critical code injection vulnerability in Oracle Jdk, published on 23 Apr 2019. 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-2019-2699 in the wild and no public exploit code.

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

## Sources

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

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