dbcve.org
P NetApplication · Rt Labs

CVE-2025-32396

HIGH · 7.5 CVSS v3.1 Published 2025-05-07
Fix available
A fix is available. Upgrade to 1.0.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An Heap-based Buffer Overflow in RT-Labs P-Net version 1.0.1 or earlier allows an attacker to induce a crash in IO devices that use the library by sending a malicious RPC packet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Heap-based buffer overflow vulnerability in RT-Labs P-Net stack's RPC packet handling. Attackers can send malformed RPC packets to trigger overflow on the heap, causing denial of service via device crash in IO devices running the affected P-Net library versions 1.0.1 and earlier.

MitigationApply vendor patch when available; until then, isolate affected IO device networks and filter unauthorized RPC traffic at network perimeter to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
P NetApplication
Affected:< 1.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify P-Net library version
    Locate the P-Net library file or executable in the system (commonly found in installation directories, /usr/lib/, or embedded within the IO device firmware). Check the file version metadata or use 'strings' or 'ldd' commands if accessible. If source code is available, inspect the version defined in version.h or CMakeLists.txt
    Affected if The installed version is 1.0.1 or earlier (anything below 1.0.2)
  2. Confirm RPC functionality is in use
    Inspect the P-Net configuration or initialization code to determine if the RPC server component is enabled. Look for RPC-related configuration flags, listening ports (typically UDP/TCP ports associated with Profinet RPC), or RPC handler registration in the application's startup logs or configuration files
    Affected if RPC packet handling is enabled and the device processes incoming RPC requests
  3. Verify network accessibility of RPC service
    Check if the IO device exposing the P-Net stack is reachable on the network. Use netstat, ss, or similar tools to identify if RPC ports are bound to accessible network interfaces. Review firewall rules and network segmentation around the device
    Affected if The device is network-accessible and can receive unsolicited RPC packets from untrusted sources
  4. Review device logs for crash indicators
    Examine system logs, device event logs, or P-Net application logs for unexpected restarts, heap corruption errors, or denial-of-service events that may indicate exploitation attempts
    Affected if Recent unexplained crashes or corruption events coincide with RPC traffic

You are affected if P-Net version is below 1.0.2, RPC handling is enabled, and the device is network-accessible to receive malformed RPC packets.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.2 or later
Fixed in 1.0.2
Interim mitigation

Apply vendor patch when available; until then, isolate affected IO device networks and filter unauthorized RPC traffic at network perimeter to reduce attack surface.

Recommended fix Moderate confidence

Upgrade to P-Net version 1.0.2

  1. 1. Identify all systems and devices using the RT-Labs P-Net library
  2. 2. Check the current version of P-Net in use by examining the library files or dependency manifests
  3. 3. Locate the official RT-Labs P-Net repository or distribution source
  4. 4. Obtain P-Net version 1.0.2 or later from the official source
  5. 5. Replace the existing P-Net library files with the updated version 1.0.2
  6. 6. Rebuild and recompile any applications or firmware that link against the P-Net library
  7. 7. Deploy the updated library to all affected IO devices
  8. 8. Verify that the devices function correctly after the update
Caveat Review release notes for any API changes or behavioral differences between 1.0.1 and 1.0.2

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in P Net Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32396 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32396 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data