Alarm data length not validated against received frame length
Impact
P-Net before 1.0.3 is vulnerable to improper handling of length parameter inconsistency. An attacker with adjacent network access and an established Application Relationship can cause an application to read past the end of the receive buffer. This affects applications that use alarm data.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.The attacker must have established an Application Relationship and 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 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. An application that copies the reported number of bytes reads past the end of the receive buffer. The attacker must have established an Application Relationship and requires ADJACENT network access. Applications that do not use the alarm data are not affected.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-115794View 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.