Cyber Resilience

CVE-2025-32399

Rt-Labs P-Net ≤ 1.0.2

Published
07 May 2025
Modified
17 June 2026
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0051 41th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

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

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

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-32402Same product: Rt-Labs P-Net
CVE-2025-32405Same product: Rt-Labs P-Net
CVE-2025-32403Same product: Rt-Labs P-Net
CVE-2025-32404Same product: Rt-Labs P-Net
CVE-2025-32396Same product: Rt-Labs P-Net
CVE-2025-32401Same product: Rt-Labs P-Net
CVE-2025-32400Same product: Rt-Labs P-Net
CVE-2025-32397Same product: Rt-Labs P-Net
CVE-2025-32398Same product: Rt-Labs P-Net
CVE-2024-8508Shared CWE-1284, CWE-606

Affected Assets

rt-labs
p-net
≤ 1.0.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V6.7.2
  • V17.3.2
  • V1.4.2
  • V2.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.

PR.PS-06 mostly match
prevents

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.

finds

Security testing in development can detect and block unchecked loop conditions before release.

prevents

Secure development lifecycle requires input validation and bounds checking that can prevent unchecked loop conditions.

prevents

Application security requirements include input validation rules that mitigate excessive looping from untrusted data.

prevents

Secure architecture principles encourage robust input handling but do not specifically address quantity validation.

prevents

Secure coding standards directly mandate validation of loop-control inputs to prevent unbounded iteration.

References