Resource exhaustion from unreleased AR and RPC session on RPC requests with incorrect endianness
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.414% 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 does not release the Application Relationship (AR) and the RPC session when an RPC request is rejected because its data representation has incorrect endianness. The session and its AR remain allocated, so repeated requests exhaust the available sessions. Once they are exhausted the device no longer answers new RPC requests, including Connect, until it is restarted. A remote unauthenticated attacker can use this to cause a denial of service. | |
| Title | Resource exhaustion from unreleased AR and RPC session on RPC requests with incorrect endianness | |
| Weaknesses | CWE-772 | |
| References |
| |
| Metrics |
cvssV4_0
|