OMR on Z processors Exposing a possible buffer over-read problem
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Eclipse OMR | Eclipse OMR | unaffected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Eclipse | Omr | — |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.298% probability within 30 days)
| Link | Providers |
|---|---|
| https://github.com/eclipse-omr/omr/pull/8073 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:eclipse:omr:0.7.0:*:*:*:*:*:*:* | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Eclipse
Eclipse omr |
|
| Vendors & Products |
Eclipse
Eclipse omr |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In the Eclipse OMR compiler component, since release 0.7.0, an optimization enabled for Eclipse OpenJ9 consumers of OMR on Z processors incorrectly handles NUL (0x00) characters during the Latin-compatible charset (UTF-8, ISO8859-1, ASCII, etc) to IBM-1047/037 translation sequence. This can cause the output byte array to be truncated, discarding the first NUL byte and all subsequent characters, and thereby exposing a possible buffer over-read problem. This issue is fixed in Eclipse OMR version 0.8.0. | |
| Title | OMR on Z processors Exposing a possible buffer over-read problem | |
| Weaknesses | CWE-125 | |
| References |
| |
| Metrics |
cvssV4_0
|