IO-device memory corruption via malicious RPC packet
Published May 7, 2025 · Updated May 7, 2025
Out-of-bounds write in RT-Labs P-Net 1.0.1 and earlier allows remote attackers to corrupt IO-device memory via a malicious RPC packet. The pf_get_ar_prm_server_request parser writes beyond its destination buffer while decoding the crafted request. No authentication or user interaction is required; reachability requires network access to an IO device processing P-Net RPC traffic, and the reported consequence is memory corruption.
Summary
What happened
Out-of-bounds write in RT-Labs P-Net 1.0.1 and earlier allows remote attackers to corrupt IO-device memory via a malicious RPC packet. The pf_get_ar_prm_server_request parser writes beyond its destination buffer while decoding the crafted request. No authentication or user interaction is required; reachability requires network access to an IO device processing P-Net RPC traffic, and the reported consequence is memory corruption.
The record
- CVE
- CVE-2025-32404
- Published
- May 7, 2025
- Updated
- May 7, 2025
- Vendor
- RT-Labs
- Product
- P-Net
- Classifications
- CWE-787, T0866
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 7, 2025CVE publishedPublication date reported by the CVE source.
- May 7, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo