# CVE-2019-11772: Memory corruption in Eclipse OpenJ9

> A missing bounds check in Eclipse OpenJ9's JIT compiler allows arbitrary memory writes, potentially enabling code execution or privilege escalation.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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:** Yes
- **Published:** 17 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pm38-595m-8jp2

## What is CVE-2019-11772?

CVE-2019-11772 is a critical memory corruption vulnerability in The Eclipse Foundation Eclipse OpenJ9, published on 17 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Eclipse OpenJ9 prior to 0.15, the String.getBytes(int, int, byte[], int) method does not verify that the provided byte array is non-null nor that the provided index is in bounds when compiled by the JIT. This allows arbitrary writes to any 32-bit address or beyond the end of a byte array within Java code run under a SecurityManager.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Eclipse Openj9.

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

Upgrade to a fixed version.

## Is CVE-2019-11772 being exploited?

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

## Other vulnerabilities in The Eclipse Foundation Eclipse OpenJ9

- [CVE-2021-41035](https://insights.sbomify.com/CVE-2021-41035/): Security feature bypass in Eclipse OMR (critical 9.8)
- [CVE-2020-27221](https://insights.sbomify.com/CVE-2020-27221/): Memory corruption in Eclipse OpenJ9 (critical 9.8)
- [CVE-2018-12547](https://insights.sbomify.com/CVE-2018-12547/): Memory corruption in Eclipse OpenJ9 (critical 9.8)
- [CVE-2018-12549](https://insights.sbomify.com/CVE-2018-12549/): Null dereference in Eclipse OpenJ9 (critical 9.8)
- [CVE-2018-12548](https://insights.sbomify.com/CVE-2018-12548/): Memory corruption in Eclipse OpenJ9 (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11772 is a critical memory corruption vulnerability in The Eclipse Foundation Eclipse OpenJ9, published on 17 Jul 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-11772 in the wild and no public exploit code.

Affected product: The Eclipse Foundation Eclipse OpenJ9. 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-11772/ (Markdown: https://insights.sbomify.com/CVE-2019-11772/index.md)
```

## Sources

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

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