First published: Tue Jul 30 2019(Updated: )
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.
Credit: emo@eclipse.org
Affected Software | Affected Version | How to fix |
---|---|---|
Eclipse Openj9 | <0.15.0 | |
Redhat Satellite | =5.8 | |
Redhat Enterprise Linux Desktop | =6.0 | |
Redhat Enterprise Linux Desktop | =7.0 | |
Redhat Enterprise Linux Server | =6.0 | |
Redhat Enterprise Linux Server | =7.0 | |
Redhat Enterprise Linux Workstation | =6.0 | |
Redhat Enterprise Linux Workstation | =7.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this vulnerability is CVE-2019-11775.
The severity of CVE-2019-11775 is high.
The affected software for CVE-2019-11775 is Eclipse OpenJ9 prior to 0.15, Redhat Satellite 5.8, Redhat Enterprise Linux Desktop 6.0 and 7.0, Redhat Enterprise Linux Server 6.0 and 7.0, and Redhat Enterprise Linux Workstation 6.0 and 7.0.
To fix CVE-2019-11775, update Eclipse OpenJ9 to version 0.15 or later.
Yes, you can find additional information for CVE-2019-11775 at the following references: [Reference 1](https://bugs.eclipse.org/bugs/show_bug.cgi?id=549601), [Reference 2](https://bugs.eclipse.org/bugs/show_bug.cgi?id=549192), [Reference 3](https://github.com/eclipse/omr/pull/4138).