NULL Pointer DereferenceWeakness · CWE-476

CVE-2025-42902

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-14

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Due to the memory corruption vulnerability in SAP NetWeaver AS ABAP and ABAP Platform, an unauthenticated attacker can send a corrupted SAP Logon Ticket or SAP Assertion Ticket to the SAP application server. This leads to a dereference of NULL which makes the work process crash. As a result, it has a low impact on the availability but no impact on the confidentiality and integrity.

Technical summary

dbcve analysis · moderate confidence

A memory corruption vulnerability in SAP NetWeaver AS ABAP and ABAP Platform allows unauthenticated attackers to send corrupted SAP Logon Tickets or SAP Assertion Tickets. This triggers a NULL pointer dereference that crashes the work process, resulting in low availability impact but no confidentiality or integrity impact.

MitigationApply the relevant SAP security patch for this vulnerability. Restrict network access to SAP application servers to minimize exposure to unauthenticated attackers until the patch can be applied.

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

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

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

Am I affected?

dbcve checks

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

Identify SAP NetWeaver AS ABAP version

Execute transaction code 'SM51' or use transaction 'SPAM' (SAP Patch Manager) to view the installed software component versions. Check the 'SAP_BASIS' component version in transaction 'SM37' or via SAP Note that lists installed components.

Affected if The installed SAP_BASIS version falls within the affected version ranges for your specific SAP NetWeaver release. Compare your version against SAP's official advisory for CVE-2025-42902.
Verify SAP Logon Ticket authentication is enabled

Check profile parameter 'login/ticket/support' using transaction 'RZ11' (parameter display) or review the default or instance profile. Also check transaction 'SAML2' or 'SICF' for active ticket-issuing services.

Affected if Parameter 'login/ticket/support' is set to '1' (enabled) or the SAP Logon Ticket issuing service (under SICF: /sap/public/bc/icf/logon) is active.
Verify SAP Assertion Ticket (SAML_assertion) is enabled

Check profile parameter 'login/assertion/ticket' via transaction 'RZ11' or inspect the ABAP system security configuration. Review transaction 'SAML2' configuration for assertion ticket issuance.

Affected if Parameter 'login/assertion/ticket' is set to a value enabling assertion ticket issuance, or the SAML2 assertion ticket service is configured and active.
Assess network exposure of SAP application servers

Review firewall rules and network configuration to determine if the SAP message server port (default 36XX) and SAP gateway ports (33XX) are accessible from untrusted networks or the internet. Use 'SAPMSS' or 'SAPGW' service entries in /etc/services or transaction 'SMMS' to identify listening ports.

Affected if SAP application server ports (message server, dialog instances) are exposed to unauthenticated network access without proper network segmentation or firewall restrictions.

Your system is affected if it runs a vulnerable SAP NetWeaver AS ABAP version AND has either SAP Logon Ticket or SAP Assertion Ticket authentication enabled AND is network-accessible to unauthenticated attackers.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply the relevant SAP security patch for this vulnerability. Restrict network access to SAP application servers to minimize exposure to unauthenticated attackers until the patch can be applied.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing4.0 h
Review / QA2.0 h

15.0 hours of engineering $2,640

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-42902?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.4%

Remediation

Need this fixed?

Have this fixed 15 hrs · Moderate

Typical engagement from $2,640

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-42902 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References