Out-of-bounds write with too many MCR blocks in a Connect request
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.
No data available yet.
Vendor Solution
Upgrade to P-Net 1.0.4 or later.
Vendor Workaround
Build P-Net with PNET_OPTION_MC_CR disabled. Multicast communication relations are not supported by P-Net, and a Connect request with MCR blocks is then rejected.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | P-Net before 1.0.4 does not check the number of MCR request blocks in a Connect request against the number of multicast communication relations that an Application Relationship has room for (PNET_MAX_MC_CR, 1 by default). Each further block is written past the end of the array, into the rest of the Application Relationship and, with more blocks, into the following one. The written data comes from the request. No established Application Relationship is needed, and the attacker requires ADJACENT network access. Builds with PNET_OPTION_MC_CR disabled are not affected. | |
| Title | Out-of-bounds write with too many MCR blocks in a Connect request | |
| Weaknesses | CWE-787 | |
| References |
| |
| Metrics |
cvssV4_0
|