Heap Buffer Over-Read in ooRexx RXAPI Queue Management Allows Process Crash
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Open Object Rexx | ooRexx | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Open Object Rexx | Oorexx |
|
Vendor Solution
Upgrade to ooRexx 5.2.0 or later.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.120% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Open Object Rexx
Open Object Rexx oorexx |
|
| Vendors & Products |
Open Object Rexx
Open Object Rexx oorexx |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Heap Buffer Over-Read in ooRexx RXAPI Queue Management Allows Process Crash |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Open Object Rexx (ooRexx) before 5.2.0, RXAPI has a heap buffer over-read in a QueueManager DataQueue::addmethod. In particular, the code blindly trusts the message.parameter1 value provided by the client as the size used to fill the data from the queueData heap buffer. An attacker sends a large parameter1 value in an ADD_TO_SESSION_QUEUE or ADD_TO_NAMED_QUEUE message and then retrieves data with a PULL_FROM_SESSION_QUEUE message. (A very large value causes a process crash.) | |
| Weaknesses | CWE-130 | |
| References |
| |
| Metrics |
cvssV3_1
|