Resource exhaustion from unreleased AR and RPC session on RPC requests with incorrect endianness
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.0.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
P-Net, an open-source PROFINET device stack used in industrial embedded devices, is affected. A remote, unauthenticated attacker can send specially formed RPC requests that leave sessions allocated, eventually preventing the device from accepting new connections until it is restarted.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- RT-Labs P-Net
fixed in 1.0.3