LiveActive security incident?Get immediate response
CVE Record

CVE-2019-11772: In Eclipse OpenJ9 prior to 0.15, the String.getBytes(int, int, byte[], int) method does not verify that the...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2019-11772 is a memory-safety flaw in Eclipse OpenJ9 before 0.15. Certain Java string byte-copy operations compiled by the JIT may skip null and bounds checks, allowing writes outside the intended byte array under a SecurityManager. That can undermine Java isolation in affected runtimes.

Executive priority

Treat as a targeted remediation item for Java estates using OpenJ9. It is not KEV-listed in the provided sources, but the potential impact on Java sandbox boundaries makes outdated OpenJ9 deployments worth finding and upgrading promptly.

Technical view

OpenJ9 JIT compilation of String.getBytes(int, int, byte[], int) failed to validate a non-null destination array and destination bounds. The CVE describes arbitrary writes to any 32-bit address or past a byte array from Java code running under SecurityManager. CWE-787 applies.

Likely exposure

Exposure is limited to systems running Eclipse OpenJ9 prior to 0.15, including environments covered by the cited Red Hat advisories. Risk is higher where Java applications run untrusted or semi-trusted code under SecurityManager assumptions.

Exploitation context

The source bundle does not show CISA KEV listing or public active exploitation. The described primitive is serious, but sources do not provide exploit maturity, required privileges beyond Java code execution, or affected downstream package details.

Researcher notes

The key constraint is JIT-compiled execution of a deprecated String.getBytes overload under SecurityManager. Sources do not include CVSS, exploit code, or detailed platform matrices. Validate exposure by runtime version and downstream vendor package status, not by product name alone.

Mitigation direction

  • Identify all Eclipse OpenJ9 runtimes and versions in production and build images.
  • Move affected OpenJ9 runtimes off versions prior to 0.15.
  • Apply applicable Red Hat security advisories for vendor-packaged Java runtimes.
  • Review vendor guidance before changing Java runtime packages.
  • Reduce exposure of workloads executing untrusted Java code.

Validation and detection

  • Inventory JVM vendor and version across hosts, containers, and CI images.
  • Confirm no runtime reports Eclipse OpenJ9 below 0.15.
  • Check package update history against the cited Red Hat advisories.
  • Review applications that depend on SecurityManager isolation assumptions.
  • Prioritize systems executing user-supplied or plugin Java code.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-11772 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
The Eclipse FoundationEclipse OpenJ9unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.