Nanomodbus
Approved changes feed: RSS · Atom
cpe:2.3:a:debevv:nanomodbus:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Debevv (d5ca693e-99ad-5e99-9ff6-d03a917b6468) |
|---|---|
| Product | Nanomodbus (27d742a9-ffe2-5b95-8828-59942313a18f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-71256 |
vulnerable | 2026-09-16 04:32:59.441738 |
nanoMODBUS Client-Side Out-of-Bounds Read Leading to Wild-Pointer Write via object_id
CRITICAL (9.8)
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].
Published: 2026-08-05T11:44:21.992Z
Updated: 2026-08-10T11:46:18.081Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-71254 |
vulnerable | 2026-09-16 04:32:59.274929 |
nanoMODBUS Server-Side Out-of-Bounds Write in handle_read_file_record()
CRITICAL (9.8)
nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus server-side handle_read_file_record function (FC 0x14, Read File Record) in nanomodbus.c. The function validates that the total request size does not exceed 245 bytes and that each sub-request's record_length is at most 124, but it never validates the CUMULATIVE response size across all sub-requests before processing them.
Published: 2026-08-05T11:44:20.214Z
Updated: 2026-08-10T11:46:13.975Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-71255 |
vulnerable | 2026-09-16 04:32:59.205062 |
nanoMODBUS Client-Side Out-of-Bounds Write via object_length in recv_read_device_identification_res()
HIGH (8.6)
nanoMODBUS through v1.23.0 contains an out-of-bounds write in the Modbus client-side recv_read_device_identification_res function (FC 0x2B/MEI 0x0E, Read Device Identification) in nanomodbus.c. The server-supplied object_length field (0-246) is validated only against the remaining PDU size (res_size_left) and is never validated against the caller-supplied buffers_length parameter.
Published: 2026-08-05T11:44:21.097Z
Updated: 2026-08-10T11:46:16.030Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-54410 |
vulnerable | 2026-07-29 01:00:27.782279 |
nanoMODBUS Off-by-One Buffer Overflow in recv_msg_header() via Crafted MBAP Length Field
HIGH (8.6)
nanoMODBUS through v1.23.0 contains an off-by-one buffer overflow in the recv_msg_header function of the Modbus/TCP server that allows remote unauthenticated attackers to write one attacker-controlled byte past the end of the 260-byte receive buffer by sending a crafted MBAP frame whose Length field is set to 255.
Published: 2026-06-14T17:10:12.275Z
Updated: 2026-08-10T11:43:54.292Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.