Out-of-bounds read of DCP block header in DCP Set and Identify request parsing
Impact
P-Net before 1.0.3 has an out-of-bounds read weakness in DCP Set and Identify request parsing, potentially causing a crash or disclosing memory content, requiring adjacent network access. The issue arises from incomplete block header checks and block length underflow. This affects P-Net versions less than 1.0.3.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Requires ADJACENT network access.
What to do
Upgrade to P-Net 1.0.3 or later.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
RT-Labs · rt-labs
P-Net
1 range
RT-Labs · rt-labs
P-Net
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → before 1.0.3
semver versions
Other versions: unaffected
Original source description
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.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-115795View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.