CVE-2025-32404
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 · uneditedAn Out-of-bounds Write in RT-Labs P-Net version 1.0.1 or earlier allows an attacker to corrupt the memory of 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 · high confidenceRT-Labs P-Net library versions 1.0.1 and earlier contain an out-of-bounds write vulnerability in RPC packet handling. Attackers can send specially crafted malicious RPC packets to corrupt memory of IO devices using this library, potentially leading to remote code execution or denial of service.
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< 1.0.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if P-Net library is installedSearch for P-Net library files or dependencies in the system. Look for files named 'p-net', 'pnet', or check package manager listings for rt-labs or P-Net packages. If using embedded systems, review the firmware/software bill of materials for the P-Net library.Affected if The P-Net library or any software using RT-Labs P-Net is found in the environment.
-
Determine the installed P-Net versionCheck the version of the P-Net library or the application that bundles it. Use commands like 'dpkg -l', 'rpm -qa', or inspect library version information if available. Review software release notes or firmware version strings.Affected if The installed version is 1.0.1 or earlier, or the version cannot be determined but is below 1.0.2.
-
Verify RPC service exposureDetermine if the system exposes Profinet RPC services. Review network configurations and identify if the device participates in Profinet IO communication. Check if ports used for Profinet RPC (typically port 0x0E0A or dynamic RPC ports) are listening or accessible.Affected if The system exposes Profinet RPC services on the network and can receive RPC packets from other devices.
-
Check network accessibility of affected serviceAssess whether the P-Net device is accessible from network segments that could contain malicious actors. Review firewall rules, VLAN segmentation, and network ACLs controlling access to industrial protocol traffic.Affected if The Profinet RPC interface is accessible from network segments that are not fully trusted or controlled.
You are affected if your environment contains any installation of the RT-Labs P-Net library version 1.0.1 or earlier that exposes Profinet RPC services to the network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.2
Upgrade P-Net library to version 1.0.2 or later which contains the fix. If upgrading is not immediately possible, network segment the affected devices and implement strict RPC packet validation at network boundaries.
1.0.2
- Upgrade RT-Labs P-Net library to version 1.0.2 or later
- Rebuild and redeploy any applications or IO devices that use the P-Net library
- Verify the upgrade was successful by confirming the library version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32404 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32404 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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