CVE-2025-42944
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 · uneditedDue to a deserialization vulnerability in SAP NetWeaver, an unauthenticated attacker could exploit the system through the RMI-P4 module by submitting malicious payload to an open port. The deserialization of such untrusted Java objects could lead to arbitrary OS command execution, posing a high impact to the application's confidentiality, integrity, and availability.
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 confidenceA deserialization vulnerability in SAP NetWeaver's RMI-P4 module allows unauthenticated attackers to execute arbitrary OS commands by submitting malicious Java deserialization payloads to open RMI-P4 ports.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 SAP NetWeaver installation and versionRun: sapcontrol -nr <instance> -function GetVersionInfo or check SAPMMC/SAP Management Console for NetWeaver version. Also check for JAVA processes: ps -ef | grep -i sapAffected if Running an unpatched SAP NetWeaver version and RMI-P4 is exposed
-
Locate and verify RMI-P4 port is listeningRun: netstat -an | grep -E '5[0-9]{4}' or nmap -p- <target> to scan for Java RMI ports. Check SAP profile parameters for P4 ports (parameter: rmi/p4/port or service/ports)Affected if RMI-P4 port is open and listening on the system
-
Check network exposure of RMI-P4 serviceRun: nmap -p <discovered_port> <target> from an external system, or verify firewall rules: iptables -L -n or Windows Firewall rules for inbound rules on the RMI-P4 portAffected if RMI-P4 port is accessible from untrusted networks (internet or less trusted zones)
-
Detect Java RMI endpoint availabilityRun: rmiregistry <port> or use a Java deserialization scanner tool like ysoserial against the discovered port to confirm it accepts serialized Java objectsAffected if The port accepts Java serialized objects without authentication
Affected if SAP NetWeaver with an open/exposed RMI-P4 port is running and the version has not been patched for this deserialization vulnerability.
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.
From vendor dataImmediately restrict network access to RMI-P4 ports, apply SAP security patches as soon as available, and implement network segmentation or WAF controls to block malicious deserialization payloads.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-42944 — 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-42944 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