Community
Participate
Working Groups
project: Eclipse OMR versions: all cwe: CWE-367 http://cwe.mitre.org/data/definitions/367.html The software checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the software to perform invalid actions when the resource is in an unexpected state. summary: 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 - see also https://nvd.nist.gov/vuln/detail/CVE-2018-1890
This problem has now been resolved by https://github.com/eclipse/omr/pull/4138
I've assigned CVE-2019-11774
The project's 0.1 release scheduled for September 18. Shall I update the version on this CVE to be "all versions prior to 0.1" and submit?
Sure, sounds reasonable to me (in the absence of any explicit way to refer to such "releases" :) )
I've created a pull-request with the central authority. https://github.com/CVEProject/cvelist/pull/2543
