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.
References
Link | Resource |
---|---|
https://access.redhat.com/errata/RHSA-2019:2494 | Third Party Advisory |
https://access.redhat.com/errata/RHSA-2019:2495 | Third Party Advisory |
https://access.redhat.com/errata/RHSA-2019:2585 | Third Party Advisory |
https://access.redhat.com/errata/RHSA-2019:2590 | Third Party Advisory |
https://access.redhat.com/errata/RHSA-2019:2592 | Third Party Advisory |
https://access.redhat.com/errata/RHSA-2019:2737 | Third Party Advisory |
https://bugs.eclipse.org/bugs/show_bug.cgi?id=549601 | Issue Tracking Vendor Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
History
No history.
Information
Published : 2019-07-30 14:15
Updated : 2024-02-28 17:08
NVD link : CVE-2019-11775
Mitre link : CVE-2019-11775
CVE.ORG link : CVE-2019-11775
JSON object : View
Products Affected
eclipse
- openj9
redhat
- enterprise_linux_workstation
- enterprise_linux_server
- satellite
- enterprise_linux_desktop
CWE
CWE-367
Time-of-check Time-of-use (TOCTOU) Race Condition