Read the docs

Integer underflow in RT-Labs P-Net IODWrite record length handling

Priority LOW 11CWE-191Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
None · None · Low
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

P-Net before 1.0.4 from RT-Labs 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 underflows when it is smaller than the header, so the record handlers receive a data length of about 65530 (CWE-191). An attacker with an established Application Relationship, or able to send in its context, and ADJACENT network access can make the fixed-size reads of the I&M and PDPort handlers read past the end of the session buffer.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

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 underflows and the handlers receive a data length of about 65530. The fixed-size reads of the I&M and PDPort handlers can then read past the end of the session buffer. The result of the write is discarded. The attacker must have an established Application Relationship or be able to send in the context of one, and requires ADJACENT network access.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00195 9th percentileScored 2026-11-16
Fix Fixed P-Net (RT-Labs): 1.0.4

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
RT-LabsP-Netbefore 1.0.41.0.4Patch availableCNA
  • P-Net VendorRT-Labs Affected before 1.0.4 Fixed in 1.0.4 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:rt-labs:p-net:*:*:*:*:*:*:*:*——RT-Labs
  • cpe:2.3:a:rt-labs:p-net:*:*:*:*:*:*:*:* Versions — — ·RT-Labs

Remediation

Update RT-Labs P-Net to version 1.0.4, which fixes the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA P-Net (RT-Labs) Fixed in 1.0.4

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    RT-Labs P-Net 1.0.4

    9 records Highest priority Priority LOW 9 LOW

    Other records, highest priority first

    • TI-2026-91525 RPC session pool exhausted by unfinished fragmented requestsPriority LOW 31
    • TI-2026-91523 Out-of-bounds write in RT-Labs P-Net via too many MCR blocksPriority LOW 31
    • TI-2026-91520 Refused IP settings are stored in P-Net DCP Set requestsPriority LOW 30

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-124758
  2. 2026-11-13 Alias added: GHSA-vcxv-jm58-q462
  3. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2026-82626 Out-of-bounds write when parsing AR Vendor Block requests in RT-Labs P-Net CVSS 4.0CRITICAL 9.3
  • TI-2026-82632 Resource exhaustion from RPC sessions kept for unknown interface requests CVSS 4.0HIGH 8.7
  • TI-2026-82630 NULL pointer dereference in RT-Labs P-Net on implicit read requests CVSS 4.0HIGH 8.7
  • TI-2026-82627 NULL pointer dereference in P-Net lets remote attackers crash devices CVSS 4.0HIGH 8.7
  • TI-2026-82625 Infinite loop in RT-Labs P-Net PDPortDataCheck record handling CVSS 4.0HIGH 8.7
  • TI-2025-23482 Out-of-bounds write in RT-Labs P-Net CVSS 3.1CRITICAL 9.8
See all 37 →

Sources