CVE-2025-32399
Rt-Labs P-Net ≤ 1.0.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LSummary
CVE-2025-32399 is a medium-severity Unchecked Input for Loop Condition (CWE-606) vulnerability in Rt-Labs P-Net. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 41th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-13674
Vulnerability Data
An Unchecked Input for Loop Condition in RT-Labs P-Net version 1.0.1 or earlier allows an attacker to cause IO devices that use the library to enter an infinite loop by sending a malicious RPC packet.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.7.2V17.3.2V1.4.2V2.1.1
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly stops untrusted values from reaching loop conditions without bounds or sanity checks.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and bounds checking that prevent unchecked loop conditions.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect and block unchecked loop conditions before release.
Secure development lifecycle requires input validation and bounds checking that can prevent unchecked loop conditions.
Application security requirements include input validation rules that mitigate excessive looping from untrusted data.
Secure architecture principles encourage robust input handling but do not specifically address quantity validation.
Secure coding standards directly mandate validation of loop-control inputs to prevent unbounded iteration.