CVE-2019-11774

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2019-11774
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2019-11774.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2019-11774
Published
2019-09-12T18:15:11.850Z
Modified
2026-03-14T09:32:23.484610Z
Severity
  • 7.4 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H CVSS Calculator
Summary
[none]
Details

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.

References

Affected packages

Git / github.com/eclipse-omr/omr

Affected ranges

Type
GIT
Repo
https://github.com/eclipse-omr/omr
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed
20db4fbc1ea570fd806783a97b16831f4f719eed
Database specific 
{
    "versions": [
        {
            "introduced": "0"
        },
        {
            "fixed": "0.1"
        }
    ]
}

Database specific

source 
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2019-11774.json"