39 matches found
CVE-2026-129814
The SDO Information Get Object Description and Get Entry Description responses copy the object or entry name into the mailbox data area and then write a null terminator byte. The copy loops ran up to the last available byte in the buffer, leaving no room for the terminator. When an object or entr...
CVE-2026-129805
An object dictionary entry can carry write-access flags and still have a NULL data pointer, for example when a constant value is held in the value field rather than in addressable storage. The CoE SDO download handler checked write access but not whether storage was present, then wrote the...
CVE-2026-129811
The PDO mapping bit lengths stored in the mapping objects are writable by the master via SDO. sizeOfPDO summed them without checking the total against the size of the rxpdo or txpdo process data buffers. A master can craft a mapping whose total bit count exceeds those buffers, causing COEpdoPack...
CVE-2026-129806
The CoE SDO upload handler enters its normal-response path used for objects longer than 4 bytes and passes objd + nsub-data directly to the pre-object handler and to the response copy. Entries that hold a constant in the value field have data set to NULL; a master can request such an entry and...
CVE-2026-129799
A CoE SDO request for index 0xFFFF matches the object list terminator entry instead of returning not-found. The terminator has a NULL objdesc pointer. Callers dereference it without checking, crashing the slave...
CVE-2026-129798
The CoE SDO segmented download handler advances a write pointer by each incoming segment's size but does not track how many bytes have been written in total. A master can keep sending non-last segments until the pointer has walked past the end of the object buffer or the complete-access staging...
CVE-2026-129796
The CoE SDO download handler for flexible-length objects VISIBLESTRING, OCTETSTRING, and similar does not check that the master-declared transfer size fits within the object before writing. Two distinct writes are affected: the VISIBLESTRING zero-padding memset and the first-frame copy into the...
CVE-2026-129811
The CoEthernet (CoE) protocol is vulnerable to an out-of-bounds write because the sizeOfPDO function fails to validate that the total bit lengths of PDO mapping objects stay within the limits of the rxpdo[] or txpdo[] process data buffers. An attacker (the master) can craft a mapping via SDO that...
CVE-2026-129811 CoE PDO Mapping Size Exceeds Process Data Buffer Out-of-Bounds Write
The PDO mapping bit lengths stored in the mapping objects are writable by the master via SDO. sizeOfPDO summed them without checking the total against the size of the rxpdo or txpdo process data buffers. A master can craft a mapping whose total bit count exceeds those buffers, causing COEpdoPack...
CVE-2026-129806
The CoE SDO upload handler is vulnerable to a NULL pointer dereference (CWE-476). The issue occurs because the handler enters its normal-response path for objects longer than 4 bytes and passes (objd + nsub)->data directly to the pre-object handler and response copy. Because entries holding a ...
CVE-2026-129806 CoE SDO Upload NULL Pointer Dereference on Dataless Entry
The CoE SDO upload handler enters its normal-response path used for objects longer than 4 bytes and passes objd + nsub-data directly to the pre-object handler and to the response copy. Entries that hold a constant in the value field have data set to NULL; a master can request such an entry and...
CVE-2026-129805
The CoE SDO download handler is vulnerable to a NULL Pointer Dereference (CWE-476) due to how it handles object dictionary entries. Specifically, while the handler validates write-access flags, it fails to verify if storage is present for entries that hold a constant value in the value field inst...
CVE-2026-129805 CoE SDO Download NULL Pointer Dereference on Dataless Entry
An object dictionary entry can carry write-access flags and still have a NULL data pointer, for example when a constant value is held in the value field rather than in addressable storage. The CoE SDO download handler checked write access but not whether storage was present, then wrote the...
CVE-2026-129800
The sizeOfPDO function in the CoE component is vulnerable to an out-of-bounds read during state transitions. The root cause is that the function uses the subindex-0 count of the SM-assign and PDO-mapping objects as loop bounds without validating them against the actual descriptor array sizes. On ...
CVE-2026-129800 CoE sizeOfPDO Descriptor Traversal Out-of-Bounds Read
sizeOfPDO, called during state transitions, uses the subindex-0 count of the SM-assign and PDO-mapping objects as loop bounds without checking those counts against the descriptor array sizes. On builds where those subindex-0 values are writable via SDO, a master can write 0xFF and cause sizeOfPDO...
CVE-2026-129799 CoE OD Sentinel NULL Pointer Dereference
A CoE SDO request for index 0xFFFF matches the object list terminator entry instead of returning not-found. The terminator has a NULL objdesc pointer. Callers dereference it without checking, crashing the slave...
CVE-2026-129799
The CoE OD Sentinel component is vulnerable to a NULL Pointer Dereference (CWE-476) when handling a CoE SDO request for index 0xFFFF . Instead of returning a
CVE-2026-129798
The CoE SDO segmented download handler is vulnerable to a Cumulative Out-of-Bounds Write (CWE-787). The root cause is that the handler advances a write pointer by each incoming segment's size but fails to track the total number of bytes written. An attacker (master) can repeatedly send non-last s...
CVE-2026-129798 CoE SDO Segmented Download Cumulative Out-of-Bounds Write
The CoE SDO segmented download handler advances a write pointer by each incoming segment's size but does not track how many bytes have been written in total. A master can keep sending non-last segments until the pointer has walked past the end of the object buffer or the complete-access staging...
CVE-2026-129797 CoE SDO Segmented Download Missing State Guard
SDOdownloadsegment is called whenever a mailbox frame carries the DOWNLOADSEGREQ command byte, regardless of whether a segmented download is actually in progress. ESCvar.data, which the handler writes through, is NULL until a segmented transfer is started. A master can send a DOWNLOADSEGREQ at an...