Rt-Labs P-Net
30 CVEs affecting Rt-Labs P-Net. Latest disclosed: 2026-11-13. Critical: 0, High: 6.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2025-32405 | High | 7.5 | 2025-05-07 | An Out-of-bounds Write in RT-Labs P-Net version 1.0.1 or earlier allows an attacker to induce a crash in IO devices that use the library by sending a malicious… |
CVE-2025-32402 | High | 7.5 | 2025-05-07 | An Out-of-bounds Write in RT-Labs P-Net version 1.0.1 or earlier allows an attacker to induce a crash in IO devices that use the library by sending a malicious… |
CVE-2025-32400 | High | 7.5 | 2025-05-07 | An Heap-based Buffer Overflow in RT-Labs P-Net version 1.0.1 or earlier allows an attacker to induce a crash in IO devices that use the library by sending a ma… |
CVE-2025-32398 | High | 7.5 | 2025-05-07 | A NULL Pointer Dereference in RT-Labs P-Net version 1.0.1 or earlier allows an attacker to induce a crash in IO devices that use the library by sending a malic… |
CVE-2025-32397 | High | 7.5 | 2025-05-07 | An Heap-based Buffer Overflow in RT-Labs P-Net version 1.0.1 or earlier allows an attacker to induce a crash in IO devices that use the library by sending a ma… |
CVE-2025-32396 | High | 7.5 | 2025-05-07 | An Heap-based Buffer Overflow in RT-Labs P-Net version 1.0.1 or earlier allows an attacker to induce a crash in IO devices that use the library by sending a ma… |
CVE-2025-32399 | Medium | 5.3 | 2025-05-07 | An Unchecked Input for Loop Condition in RT-Labs P-Net version 1.0.1 or earlier allows an attacker to cause IO devices that use the library to enter an infinit… |
CVE-2025-32404 | Medium | 4.8 | 2025-05-07 | An Out-of-bounds Write in RT-Labs P-Net version 1.0.1 or earlier allows an attacker to corrupt the memory of IO devices that use the library by sending a malic… |
CVE-2025-32403 | Medium | 4.8 | 2025-05-07 | An Out-of-bounds Write in RT-Labs P-Net version 1.0.1 or earlier allows an attacker to corrupt the memory of IO devices that use the library by sending a malic… |
CVE-2025-32401 | Medium | 4.8 | 2025-05-07 | An Heap-based Buffer Overflow in RT-Labs P-Net version 1.0.1 or earlier allows an attacker to corrupt the memory of IO devices that use the library by sending… |
CVE-2026-127125 | | 2026-11-13 | P-Net before 1.0.4 aborts the Application Relationship of an RPC session when a fragment of a response has been resent without being acknowledged, without chec… | |
CVE-2026-127124 | | 2026-11-13 | P-Net before 1.0.4 keeps the RPC session that is allocated for a fragment of a request with an unknown activity UUID, without a timeout, when the rest of the r… | |
CVE-2026-127123 | | 2026-11-13 | P-Net before 1.0.4 releases the Application Relationship of an RPC session, without the abort procedure, when a fragment of a request has another data represen… | |
CVE-2026-127122 | | 2026-11-13 | P-Net before 1.0.4 does not check the number of MCR request blocks in a Connect request against the number of multicast communication relations that an Applica… | |
CVE-2026-124762 | | 2026-11-13 | P-Net before 1.0.4 finds the RPC session of a received PDU by its activity UUID only, and a reject, fault or cancel PDU for the session aborts the Application… | |
CVE-2026-124761 | | 2026-11-13 | P-Net before 1.0.4 copies the IP suite of a DCP Set request to the current and the non-volatile configuration, and starts saving it, before the state of the de… | |
CVE-2026-124760 | | 2026-11-13 | P-Net before 1.0.4 sets the alarm receiver state to waiting for confirmation before the data of a received alarm notification is parsed. If the parsing fails t… | |
CVE-2026-124759 | | 2026-11-13 | 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 t… | |
CVE-2026-124758 | | 2026-11-13 | P-Net before 1.0.4 does not check the record data length of an IODWrite request to a non-user record index against the size of the record block header. The 32-… | |
CVE-2026-115795 | | 2026-10-29 | P-Net before 1.0.3 does not check that a complete block header is present in the received data before reading the next block in DCP Set and Identify requests… |