Eclipse Omr
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Eclipse Omr.
By the Year
In 2025 there have been 2 vulnerabilities in Eclipse Omr with an average score of 6.7 out of ten. Omr did not have any published security vulnerabilities last year. That is, 2 more vulnerabilities have already been reported in 2025 as compared to last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2025 | 2 | 6.65 |
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 0 | 0.00 |
| 2021 | 0 | 0.00 |
| 2020 | 0 | 0.00 |
| 2019 | 2 | 7.60 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Omr vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Eclipse Omr Security Vulnerabilities
In Eclipse OMR versions 0.2.0 to 0.4.0, some of the z/OS atoe print functions use a constant length buffer for string conversion
CVE-2025-1471
7.8 - High
- February 21, 2025
In Eclipse OMR versions 0.2.0 to 0.4.0, some of the z/OS atoe print functions use a constant length buffer for string conversion. If the input format string and arguments are larger than the buffer size then buffer overflow occurs. Beginning in version 0.5.0, the conversion buffers are sized correctly and checked appropriately to prevent buffer overflows.
In Eclipse OMR
CVE-2025-1470
5.5 - Medium
- February 21, 2025
In Eclipse OMR, from the initial contribution to version 0.4.0, some OMR internal port library and utilities consumers of z/OS atoe functions do not check their return values for NULL memory pointers or for memory allocation failures. This can lead to NULL pointer dereference crashes. Beginning in version 0.5.0, internal OMR consumers of atoe functions handle NULL return values and memory allocation failures correctly.
Prior to 0.1, AIX builds of Eclipse OMR contain unused RPATHs
CVE-2019-11773
7.8 - High
- September 12, 2019
Prior to 0.1, AIX builds of Eclipse OMR contain unused RPATHs which may facilitate code injection and privilege elevation by local users.
DLL preloading
Prior to 0.1, all builds of Eclipse OMR contain a bug where the loop versioner may fail to privatize a value
CVE-2019-11774
7.4 - High
- September 12, 2019
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.
TOCTTOU
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Eclipse Omr or by Eclipse? Click the Watch button to subscribe.
