Buffer Overflow in Eclipse OMR Processor Feature Retrieval API
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 Foundation | 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.486% probability within 30 days)
| Link | Providers |
|---|---|
| https://github.com/eclipse-omr/omr/pull/8082 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Buffer Overflow in Eclipse OMR Processor Feature Retrieval API |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-120 | |
| CPEs | cpe:2.3:a:eclipse:omr:*:*:*:*:*:*:*:* | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Eclipse
Eclipse omr |
|
| Vendors & Products |
Eclipse
Eclipse omr |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In the Eclipse OMR port library component since release 0.2.0, an API function to return the textual names of all supported processor features was not accounting for the separator inserted between processor features. If the output buffer supplied to this function was incorrectly sized, failing to account for the separator when determining when a write to the buffer was safe could lead to a buffer overflow. This issue is fixed in Eclipse OMR version 0.8.0. | |
| Weaknesses | CWE-131 | |
| References |
| |
| Metrics |
cvssV4_0
|