dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-42963

CRITICAL · 9.1 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable 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 critical vulnerability in SAP NetWeaver Application server for Java Log Viewer enables authenticated administrator users to exploit unsafe Java object deserialization. Successful exploitation can lead to full operating system compromise, granting attackers complete control over the affected system. This results in a severe impact on the confidentiality, integrity, and availability of the application and host environment.

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 confidence

A critical unsafe Java object deserialization flaw in SAP NetWeaver Application Server for Java's Log Viewer component allows authenticated administrator users to deserialize untrusted Java objects, potentially executing arbitrary code and achieving full operating system compromise.

MitigationApply the latest SAP security patches immediately, restrict administrative access to the Log Viewer component, implement network segmentation, and monitor for indicators of compromise while prioritizing critical systems.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

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

  1. Verify Log Viewer component is accessible
    Access the SAP NetWeaver Administrator (NWA) interface and navigate to the Log Viewer component. Typically found under Troubleshooting > Logs > Log Viewer, or via URL path /sap/bc/uz_man4j/logviewer. Check if the component responds without authentication errors.
    Affected if Log Viewer is exposed and accessible without proper access controls, or accessible to low-privileged users.
  2. Determine SAP NetWeaver AS Java version
    In SAP NWA, go to System > Properties > Version Info, or use transaction SE38 and run program RSNWH_VERSIONS. Alternatively, check the SAP J2EE Engine version via the Visual Administrator or deployment descriptors in the usr/sap directory.
    Affected if Installed version falls within the vulnerable version range for this CVE (specific ranges should be compared against SAP security notes).
  3. Confirm administrative access exists
    Verify if administrator roles are assigned to any users in SAP NetWeaver. Check via Identity Management in NWA or transaction SU01 for user role assignments. The Log Viewer requires administrative privileges.
    Affected if Any user account with administrative access to the Log Viewer component exists in the system.
  4. Review recent admin activity in logs
    Examine SAP system logs (via Log Viewer itself) for suspicious deserialization calls, unusual Java class loading, or unexpected commands executed around the time of potential exploitation. Look for entries containing java.io.ObjectInputStream or similar deserialization patterns.
    Affected if Unusual deserialization activity or suspicious commands appear in system logs originating from Log Viewer access.
  5. Check for unauthorized admin accounts
    In NWA Identity Management, review all accounts with SAP_J2EE_ADMIN, SAP_XP_DEV, or Log Viewer roles. Compare against expected administrator list. Check for accounts created recently or with unexpected privileges.
    Affected if Unexpected administrator accounts exist, or legitimate admin accounts show login activity from unknown sources.

A user is affected if the Log Viewer component is enabled and accessible, the SAP NetWeaver AS Java version is within the vulnerable range, and any authenticated administrator account can exploit the unsafe deserialization flaw to execute arbitrary code.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the latest SAP security patches immediately, restrict administrative access to the Log Viewer component, implement network segmentation, and monitor for indicators of compromise while prioritizing critical systems.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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