LiveActive security incident?Get immediate response
CVE Record

CVE-2019-11775: All builds of Eclipse OpenJ9 prior to 0.15 contain a bug where the loop versioner may fail to privatize a v...

All builds of Eclipse OpenJ9 prior to 0.15 contain a bug where the loop versioner may fail to privatize a value that is pulled out of the loop by versioning - for example if there is a condition that is moved out of the loop that reads a field we may not privatize the value of that field in the modified copy of the loop allowing the test to see one value of the field and subsequently the loop to see a modified field value without retesting the condition moved out of the loop. This can lead to a variety of different issues but read out of array bounds is one major consequence of these problems.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-11775 is a bug in Eclipse OpenJ9 before version 0.15. The Java runtime’s optimizer could make an unsafe assumption about data inside a loop, potentially causing memory to be read outside an array boundary. Business urgency depends on whether older OpenJ9 runtimes remain in production.

Executive priority

Treat this as an inventory-driven remediation item. It is not KEV-listed in the provided data, but older Java runtimes in production can create hidden business risk. Prioritize systems running pre-0.15 OpenJ9, especially externally exposed or high-value services.

Technical view

The issue is in OpenJ9’s loop versioner. A value moved out of a loop may not be privatized, allowing a condition check to observe one field value while the loop later observes a changed value without retesting. The source notes out-of-bounds array reads as a major consequence and maps the issue to CWE-367.

Likely exposure

Exposure is likely limited to systems running Eclipse OpenJ9 builds prior to 0.15, including environments using vendor-distributed OpenJ9 packages referenced by Red Hat advisories. The provided sources do not identify other Java runtimes as affected.

Exploitation context

The source bundle does not cite active exploitation, and KEV status is false. The available description indicates a runtime optimizer flaw with possible out-of-bounds reads, but does not provide public evidence of exploitation, exploit maturity, or attacker prerequisites.

Researcher notes

Evidence is limited to the CVE description, Eclipse bug reference, and Red Hat advisories. No CVSS vector is present in the bundle. Analysis should focus on confirming OpenJ9 use, version lineage, and whether affected packages came from the listed Red Hat updates.

Mitigation direction

  • Inventory Java runtimes and identify Eclipse OpenJ9 versions below 0.15.
  • Upgrade affected OpenJ9 installations to version 0.15 or later where applicable.
  • Apply relevant Red Hat security advisories for Red Hat-managed packages.
  • Check Eclipse and vendor guidance for environment-specific remediation details.

Validation and detection

  • Confirm runtime vendor and version across servers, containers, and build images.
  • Search dependency and base-image inventories for Eclipse OpenJ9 before 0.15.
  • Verify Red Hat advisory updates are installed where those packages are used.
  • Prioritize validation on production Java services handling untrusted inputs.
Prepared
Confidence
medium
Sources
9

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-367: 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-11775 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
8Source 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-367 · source CWE mapping

Time-of-check Time-of-use (TOCTOU) Race Condition

Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.