Alarm data length not validated against received frame length
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| RT-Labs | P-Net | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Rt-labs | P-net |
|
Vendor Solution
Upgrade to P-Net 1.0.3 or later.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.176% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Rt-labs
Rt-labs p-net |
|
| Vendors & Products |
Rt-labs
Rt-labs p-net |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Alarm data length not validated against received frame length | |
| Weaknesses | CWE-130 | |
| References |
| |
| Metrics |
cvssV4_0
|