dbcve.org
P NetApplication · Rt Labs

CVE-2025-32398

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
A NULL Pointer Dereference 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

RT-Labs P-Net versions 1.0.1 and earlier contain a NULL pointer dereference vulnerability in RPC packet handling. An attacker can send a maliciously crafted RPC packet to trigger the dereference, causing a crash (denial of service) in IO devices that use the library.

MitigationApply vendor patches when available; otherwise, implement input validation in RPC packet parsing to ensure pointers are valid before dereferencing. Network segmentation can reduce exposure to unauthenticated RPC attacks.

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. Confirm RT-Labs P-Net installation
    Identify whether RT-Labs P-Net stack or library is present in the environment. Check application dependencies, installed packages, or embedded library listings that reference 'p-net' or 'rt-labs'.
    Affected if RT-Labs P-Net is installed and in use.
  2. Determine installed P-Net version
    Query the installed P-Net library version through the application's about, version information, package manager, or library file metadata. Compare against the affected range: versions 1.0.1 and earlier are vulnerable; version 1.0.2 or later contains the fix.
    Affected if The installed version is 1.0.1 or earlier (any version below 1.0.2).
  3. Verify RPC packet handling is active
    Determine whether the P-Net stack is configured to process PROFINET IO RPC packets. Check application configuration or runtime logs for RPC listener status, IO device initialization, or PNIO stack activity.
    Affected if RPC packet handling is enabled and the IO device is operational, creating the attack surface.
  4. Assess network exposure of RPC service
    Evaluate whether the P-Net device RPC port is accessible from untrusted network segments. Identify if the device is directly exposed to attackers or behind proper network segmentation.
    Affected if The RPC service is reachable from network segments where unauthenticated attackers could send malicious packets.

You are affected if RT-Labs P-Net version 1.0.1 or earlier is installed and the IO device with RPC packet handling is network-accessible to attackers.

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 patches when available; otherwise, implement input validation in RPC packet parsing to ensure pointers are valid before dereferencing. Network segmentation can reduce exposure to unauthenticated RPC attacks.

Recommended fix Moderate confidence

P Net 1.0.2

  1. 1. Identify all systems and devices running RT-Labs P-Net library version 1.0.1 or earlier
  2. 2. Obtain the fixed version P-Net 1.0.2 from the official RT-Labs distribution source
  3. 3. Replace the vulnerable P-Net library files with version 1.0.2 on all affected IO devices
  4. 4. Reboot or restart the IO devices to ensure the new library is loaded
  5. 5. Verify that the devices are functioning correctly after the upgrade

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

Fix this in P Net Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32398 — 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-32398 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