CVE-2026-115795: Out-of-bounds read of DCP block header in DCP Set and Identify request parsing
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. If the last block ends at the end of the receive buffer, the block length of the following block is read past the end of the buffer. In addition, a DCP Set block with a length smaller than the two-byte block qualifier makes the length underflow, so the block is processed with a length of 65534 bytes. This can cause a crash (denial of service) or disclose a small amount of memory content. Requires ADJACENT network access.
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
P-Netto a version that resolves this vulnerability.Fixed in 1.0.3
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Systems using P-Net versions before 1.0.3 are affected when they process DCP Set or Identify requests. Exploitation requires adjacent-network access.
What does an attacker need to send to trigger the flaw?
An attacker can send a DCP request where the last block ends exactly at the receive-buffer boundary, causing parsing of the next block header past the buffer. A DCP Set block shorter than the two-byte block qualifier can also trigger a length underflow and processing with a length of 65534 bytes.
What is the expected impact of successful exploitation?
The issue can cause a crash, resulting in denial of service. It may also disclose a small amount of memory content.