CVE-2019-11774

HIGH
7.4
CVSS Score
Published: September 12, 2019 at 05:25 PM UTC
Updated: June 17, 2026 at 02:13 AM UTC
1 product affected across 1 vendorOmr

Using Eclipse OMR by The Eclipse Foundation?

Get instant alerts when new vulnerabilities affect Eclipse OMR - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.4
Exploit prediction
EPSS 0.7%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 0.1
Affected range stops below 0.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

x_refsource_CONFIRMPatchVendor Advisory
https://bugs.eclipse.org/bugs/show_bug.cgi?id=549192

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-367

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card