Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
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.
Vendor 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.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 13 Nov 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Alarm frames are accepted from any source address | |
| Weaknesses | CWE-346 | |
| References |
| |
| Metrics |
cvssV4_0
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: rt-labs
Published:
Updated: 2026-11-13T13:22:56.820Z
Reserved: 2026-11-09T12:48:59.071Z
Link: CVE-2026-124759
No data.
No data.
No data.
OpenCVE Enrichment
No data.
-
CWE-346
Origin Validation Error