Skip to content

Vendor

RT-Labs AB vulnerabilities

38 published CVES affecting RT-Labs AB, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
38
Critical
4
High
24
Medium
7
Low
3
Unscored
0
CISA KEV
0
Atom feed of RT-Labs AB alerts

Products

Latest RT-Labs AB CVEs

Newest publication first · page 1 of 2

  1. HighCVSS 7.1 EPSS 0.20%

    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 request never arrives. A session that does not get an Application Relationship is also kept after the response. Repeated f...

  2. HighCVSS 7.1 EPSS 0.15%

    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 device is checked. If the request is refused, for example because an Application Relationship is active, the configuration...

  3. LowCVSS 2.3 EPSS 0.19%

    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-bit length is reduced by the header size before it is passed to the record handlers, so a length smaller than the header...

  4. HighCVSS 7.1 EPSS 0.11%

    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 sing...

  5. LowCVSS 2.3 EPSS 0.18%

    P-Net before 1.0.3 passes the application alarm callback a data length derived from the variable part length field of a received RTA alarm frame without checking it against the length of the received frame. A short frame can make the callback receive a length of up to 65507 bytes...

  6. CriticalCVSS 9.3 EPSS 0.40%

    P-Net before 1.0.3, when built with PNET_OPTION_AR_VENDOR_BLOCKS enabled, parses a data length from a field of the ARVendorBlock request that is not part of the block definition and uses it as the number of bytes to copy into a fixed-size buffer, without comparing it with the buf...

  7. HighCVSS 8.7 EPSS 0.40%

    P-Net before 1.0.3 enters an infinite loop when handling a read request for the PDPortDataCheck record with subslot 0 (whole module). The loop over the ports never advanced to the next port, so the request never completes and the device stops responding. A remote unauthenticated...

  8. HighCVSS 7.1 EPSS 0.17%

    SOEM version 2.0.0 and earlier contains multiple vulnerabilities in frame processing where a malicious device can cause the master to read data outside allocated buffers. The software uses length and offset values from device messages without validating them against buffer sizes....

  9. MediumCVSS 6.5 EPSS 0.17%

    SOEM version 2.0.0 and earlier contains a vulnerability where a malicious device can crash the master system. When the software receives an error response, it clears an internal pointer but continues processing. If another message arrives before timeout, the software attempts to...

  10. MediumCVSS 6.5 EPSS 0.17%

    SOEM version 2.0.0 and earlier contains a vulnerability during device configuration where a malicious device can cause memory corruption. The software writes configuration data to a fixed-size array without checking if the array index exceeds its maximum size of EC_MAXFMMU entrie...

  11. HighCVSS 8.8 EPSS 0.21%

    SOEM version 2.0.0 and earlier contains a vulnerability in multi-segment data transfers where a malicious device can overflow memory buffers. The software checks the total size only once at the beginning, but doesn't track the cumulative size as multiple segments arrive. An attac...

  12. MediumCVSS 6.5 EPSS 0.17%

    SOEM version 2.0.0 and earlier contains vulnerabilities where a malicious device can send messages that cause the master to read data from memory locations beyond the intended buffer. The software uses length values from device responses without validating them against actual buf...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.