CVE-2019-11774
First published: Thu Sep 12 2019(Updated: )
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.
Credit: emo@eclipse.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Eclipse OMR | <0.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-11774?
CVE-2019-11774 has a severity rating that indicates a potential vulnerability affecting certain builds of Eclipse OMR.
How do I fix CVE-2019-11774?
To fix CVE-2019-11774, upgrade to Eclipse OMR version 0.1 or higher.
Which versions of Eclipse OMR are affected by CVE-2019-11774?
All builds of Eclipse OMR prior to version 0.1 are affected by CVE-2019-11774.
What kind of vulnerability is CVE-2019-11774?
CVE-2019-11774 is a bug related to the failure of the loop versioner to properly privatize a value pulled out of a loop.
Who is affected by CVE-2019-11774?
Developers and users of Eclipse OMR versions before 0.1 are affected by CVE-2019-11774.
- collector/nvd-index
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/severity
- agent/author
- agent/weakness
- agent/remedy
- agent/last-modified-date
- agent/softwarecombine
- agent/event
- agent/description
- agent/first-publish-date
- agent/tags
- agent/source
- vendor/eclipse
- canonical/eclipse omr