Soem
Monthly
Out-of-bounds reads in the SOEM EtherCAT master library (2.0.0 and earlier) let a malicious or compromised device on the same EtherCAT segment make the master read past the end of allocated buffers, disclosing memory contents or crashing the master process. No authentication or user interaction is required, but the attack surface is confined to the adjacent Layer-2 fieldbus segment - typically an isolated OT control network rather than anything internet-routable. No public exploit code or confirmed in-the-wild exploitation is identified in the available data, and the vuln.today decision label is this_week, reflecting a genuine but bounded industrial/OT priority rather than an internet-wide emergency.
Memory corruption in rt-labs SOEM 2.0.0 and earlier allows a malicious or compromised EtherCAT slave device on the same fieldbus segment to overflow master-side buffers during multi-segment data transfers, writing attacker-controlled data beyond buffer boundaries with potential for code execution. Because SOEM validates only the declared total size at the start of a transfer and never tracks cumulative size as further segments arrive, a device that declares a small initial size can pass validation and then exceed the allocation. The flaw is scored 8.8 (AV:A/AC:L/PR:N/UI:N) - unauthenticated and requiring no user interaction, but gated by an adjacent-network precondition: the attacker must already sit on the EtherCAT segment and be able to act as or subvert a slave. No public exploit code was identified at time of analysis and there is no CISA KEV entry; priority is to address it this week, and fieldbus segmentation significantly bounds exposure.
Memory corruption in SOEM (Simple Open EtherCAT Master) 2.0.0 and earlier lets a malicious or compromised device on the EtherCAT segment drive manipulated message length values through unvalidated arithmetic, producing negative or oversized results that bypass bounds checks and cause writes outside allocated memory. The flaw is rated CVSS 8.3 (AV:A/AC:L/PR:N/UI:N, C:L/I:H/A:H) and affects masters built on the library during normal message processing - no authentication or user interaction is needed, but the attacker must already have a presence on the same fieldbus segment as the master, so internet-facing remote exploitation is not indicated. No public exploit code or CISA KEV entry was identified at time of analysis, and the vuln.today decision label is 'this_week', reflecting a genuine priority for EtherCAT automation operators rather than a drop-everything emergency.
SOEM (Simple Open EtherCAT Master) 2.0.0 and earlier can be crashed by a malicious device on the same EtherCAT segment: an error response causes the library to clear an internal pointer while continuing to process, and a second message arriving before the timeout makes the master dereference that cleared pointer. The result is a NULL pointer dereference that takes down the master process, so impact is limited to availability (CVSS 6.5, AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with no code execution or data exposure. Exploitation requires the attacker to be a device on the local fieldbus, no public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor advisory RRTL-260921-01 documents the issue.
Memory corruption in the rt-labs SOEM EtherCAT master library (version 2.0.0 and earlier) allows a malicious or compromised EtherCAT slave device to derail the master's device-configuration routine: by presenting more than EC_MAXFMMU FMMU configuration blocks, the slave forces out-of-bounds writes past a fixed-size array, and the resulting corruption of adjacent memory can disrupt subsequent master operation. The issue is scored CVSS 3.1 6.5 (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), so impact is confined to availability - no confidentiality or integrity loss and no confirmed code execution - and the main precondition is that an attacker can place or control a device on the adjacent EtherCAT segment. No public exploit code or confirmed active exploitation was identified at time of analysis; the vendor advisory RRTL-260921-01 is available.
An out-of-bounds read in the SOEM EtherCAT master library (version 2.0.0 and earlier) lets a malicious or compromised EtherCAT slave device send a response whose length field exceeds the actual payload, causing the master to over-read up to 64KB of its own memory and return that data to the attacker. Exploitation requires a foothold on the same EtherCAT network segment as the SOEM-based master - the flaw is not reachable over the public internet - and no authentication or user interaction is needed because EtherCAT has no native device authentication. Impact is confidentiality-only (memory disclosure); no integrity or availability effect is described, and no public exploit code or confirmed active exploitation was identified at time of analysis, though the vendor has published an advisory.
Out-of-bounds reads in the SOEM EtherCAT master library (2.0.0 and earlier) let a malicious or compromised device on the same EtherCAT segment make the master read past the end of allocated buffers, disclosing memory contents or crashing the master process. No authentication or user interaction is required, but the attack surface is confined to the adjacent Layer-2 fieldbus segment - typically an isolated OT control network rather than anything internet-routable. No public exploit code or confirmed in-the-wild exploitation is identified in the available data, and the vuln.today decision label is this_week, reflecting a genuine but bounded industrial/OT priority rather than an internet-wide emergency.
Memory corruption in rt-labs SOEM 2.0.0 and earlier allows a malicious or compromised EtherCAT slave device on the same fieldbus segment to overflow master-side buffers during multi-segment data transfers, writing attacker-controlled data beyond buffer boundaries with potential for code execution. Because SOEM validates only the declared total size at the start of a transfer and never tracks cumulative size as further segments arrive, a device that declares a small initial size can pass validation and then exceed the allocation. The flaw is scored 8.8 (AV:A/AC:L/PR:N/UI:N) - unauthenticated and requiring no user interaction, but gated by an adjacent-network precondition: the attacker must already sit on the EtherCAT segment and be able to act as or subvert a slave. No public exploit code was identified at time of analysis and there is no CISA KEV entry; priority is to address it this week, and fieldbus segmentation significantly bounds exposure.
Memory corruption in SOEM (Simple Open EtherCAT Master) 2.0.0 and earlier lets a malicious or compromised device on the EtherCAT segment drive manipulated message length values through unvalidated arithmetic, producing negative or oversized results that bypass bounds checks and cause writes outside allocated memory. The flaw is rated CVSS 8.3 (AV:A/AC:L/PR:N/UI:N, C:L/I:H/A:H) and affects masters built on the library during normal message processing - no authentication or user interaction is needed, but the attacker must already have a presence on the same fieldbus segment as the master, so internet-facing remote exploitation is not indicated. No public exploit code or CISA KEV entry was identified at time of analysis, and the vuln.today decision label is 'this_week', reflecting a genuine priority for EtherCAT automation operators rather than a drop-everything emergency.
SOEM (Simple Open EtherCAT Master) 2.0.0 and earlier can be crashed by a malicious device on the same EtherCAT segment: an error response causes the library to clear an internal pointer while continuing to process, and a second message arriving before the timeout makes the master dereference that cleared pointer. The result is a NULL pointer dereference that takes down the master process, so impact is limited to availability (CVSS 6.5, AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) with no code execution or data exposure. Exploitation requires the attacker to be a device on the local fieldbus, no public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor advisory RRTL-260921-01 documents the issue.
Memory corruption in the rt-labs SOEM EtherCAT master library (version 2.0.0 and earlier) allows a malicious or compromised EtherCAT slave device to derail the master's device-configuration routine: by presenting more than EC_MAXFMMU FMMU configuration blocks, the slave forces out-of-bounds writes past a fixed-size array, and the resulting corruption of adjacent memory can disrupt subsequent master operation. The issue is scored CVSS 3.1 6.5 (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), so impact is confined to availability - no confidentiality or integrity loss and no confirmed code execution - and the main precondition is that an attacker can place or control a device on the adjacent EtherCAT segment. No public exploit code or confirmed active exploitation was identified at time of analysis; the vendor advisory RRTL-260921-01 is available.
An out-of-bounds read in the SOEM EtherCAT master library (version 2.0.0 and earlier) lets a malicious or compromised EtherCAT slave device send a response whose length field exceeds the actual payload, causing the master to over-read up to 64KB of its own memory and return that data to the attacker. Exploitation requires a foothold on the same EtherCAT network segment as the SOEM-based master - the flaw is not reachable over the public internet - and no authentication or user interaction is needed because EtherCAT has no native device authentication. Impact is confidentiality-only (memory disclosure); no integrity or availability effect is described, and no public exploit code or confirmed active exploitation was identified at time of analysis, though the vendor has published an advisory.