Prior to 0.1, all builds of Eclipse OMR contain a bug where the loop versioner may fail to privatize a value that is pulled out of the…

Description

Prior to 0.1, all builds of Eclipse OMR 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.

Scores

EPSS (exploitation in 30 days)

0.67% · top 48% of all CVEs (7 Nov 2026)

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.4.

Weakness

• CWE-367 (opens in a new tab)All about CWE-367 and its CVEs

Affected products

• The Eclipse Foundation · Eclipse OMR

  • affected unspecified – < 0.1

References (1)

• https://bugs.eclipse.org/bugs/show_bug.cgi?id=549192 (opens in a new tab)x_refsource_CONFIRMx_transferred

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2019-11774](https://trackcve.app/badge/CVE-2019-11774.svg)](https://trackcve.app/cve/CVE-2019-11774)

Record last updated 4 Aug 2024, 23:03 UTC.