RT-Labs P-Net
Alarm frames are accepted from any source address
P-Net before 1.0.4 routes a received RTA alarm frame to an Application Relationship using only the destination alarm reference in the frame, without checking the source of the frame. A host with ADJACENT network access can abort an established Application Relationship with a single alarm ERROR frame, or deliver forged alarm notifications with chosen type, slot, subslot, USI and payload to the application.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 1.0.4
- >= 1.0.4, < *
Fixed in 1.0.4, *
Mitigation
Upgrade to P-Net 1.0.4 or later, which ignores alarm frames that do not come from the IO-controller of the Application Relationship. It reduces the risk but does not remove it, see Remaining Risk.
Workaround
Isolate the network of the device from untrusted hosts, for example by a firewall or a separate network,. The remaining risk is that a host on the network that knows the MAC address of the IO-controller and the alarm references can still send forged alarm frames.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.