nanoMODBUS Client-Side Out-of-Bounds Read Leading to Wild-Pointer Write via object_id
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| debevv | nanoMODBUS | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Debevv | Nanomodbus |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.553% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Description | nanoMODBUS through v1.23.0 contains an out-of-bounds stack read leading to a wild-pointer write in nmbs_read_device_identification_basic() / recv_read_device_identification_res() in nanomodbus.c. A fixed 3-element stack array order[3] = {0,1,2} maps object IDs to buffer indices. The server-supplied object_id field (0-255, read directly from the wire) is used without any bounds check as buf_index = order[object_id]. When a malicious Modbus server sends a Read Device Identification response with object_id >= 3, this reads an out-of-bounds/garbage byte from the stack adjacent to order[], which is then used as an index into a 3-element buffers[] array of char* pointers. The resulting wild pointer is passed to strncpy() as the destination, causing an arbitrary-address write with server-controlled data. | nanoMODBUS through v1.23.0 contains an out-of-bounds stack read leading to a wild-pointer write in nmbs_read_device_identification_basic / recv_read_device_identification_res in nanomodbus.c. A fixed 3-element stack array order[3] = {0,1,2} maps object IDs to buffer indices. The server-supplied object_id field (0-255, read directly from the wire) is used without any bounds check as buf_index = order[object_id]. |
| Title | nanoMODBUS - Client-Side Out-of-Bounds Read Leading to Wild-Pointer Write via object_id | nanoMODBUS Client-Side Out-of-Bounds Read Leading to Wild-Pointer Write via object_id |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | nanoMODBUS Client-Side Out-of-Bounds Read Leading to Wild-Pointer Write via object_id | nanoMODBUS - Client-Side Out-of-Bounds Read Leading to Wild-Pointer Write via object_id |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Debevv
Debevv nanomodbus |
|
| Vendors & Products |
Debevv
Debevv nanomodbus |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | nanoMODBUS through v1.23.0 contains an out-of-bounds stack read leading to a wild-pointer write in nmbs_read_device_identification_basic() / recv_read_device_identification_res() in nanomodbus.c. A fixed 3-element stack array order[3] = {0,1,2} maps object IDs to buffer indices. The server-supplied object_id field (0-255, read directly from the wire) is used without any bounds check as buf_index = order[object_id]. When a malicious Modbus server sends a Read Device Identification response with object_id >= 3, this reads an out-of-bounds/garbage byte from the stack adjacent to order[], which is then used as an index into a 3-element buffers[] array of char* pointers. The resulting wild pointer is passed to strncpy() as the destination, causing an arbitrary-address write with server-controlled data. | |
| Title | nanoMODBUS Client-Side Out-of-Bounds Read Leading to Wild-Pointer Write via object_id | |
| Weaknesses | CWE-125 | |
| References |
| |
| Metrics |
cvssV3_1
|