dbcve.org
NULL Pointer DereferenceWeakness · CWE-476

CVE-2024-47586

MEDIUM · 5.3 CVSS v3.1 Published 2024-11-12
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 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
SAP NetWeaver Application Server for ABAP and ABAP Platform allows an unauthenticated attacker to send a maliciously crafted http request which could cause a null pointer dereference in the kernel. This dereference will result in the system crashing and rebooting, causing the system to be temporarily unavailable. There is no impact on Confidentiality or Integrity.

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

A remote, unauthenticated attacker can send a specially crafted HTTP request to SAP NetWeaver Application Server for ABAP and ABAP Platform that triggers a null pointer dereference in the kernel. This causes the system to crash and reboot, resulting in temporary unavailability. The vulnerability has no impact on confidentiality or integrity, only availability.

MitigationApply the relevant SAP security patch when available. In the interim, consider implementing network-level filtering or a Web Application Firewall (WAF) to block potentially malicious HTTP requests targeting the affected SAP services.

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
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? 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. Identify if SAP NetWeaver ABAP is installed
    Check for SAP NetWeaver processes or services running on the system. Common process names include disp+work, msg_server, or sapgw*. On Windows, check Services for SAP* services. On Unix/Linux, run 'ps -ef | grep -i sap' or check /usr/sap/ directory structure.
    Affected if SAP NetWeaver Application Server for ABAP or ABAP Platform is installed and running
  2. Determine the ABAP version
    Check the SAP system version via transaction SM51 (Release Notes) or by examining the kernel files. The kernel version can be found in the /usr/sap/*/SYS/exe/run/ directory (Unix) or the corresponding Windows path. Compare against any known affected version ranges provided by SAP security notes.
    Affected if The installed version falls within the affected version range (if known) or is an unpatched SAP NetWeaver ABAP version
  3. Verify HTTP service exposure
    Check if SAP HTTP services (typically ports 80, 443, 8000, 8080, or sapgw* ports) are listening on network interfaces accessible from outside. Use 'netstat -an | grep -E "(80|443|8000|8080)"' or similar commands. Confirm if the ICM (Internet Communication Manager) is configured and exposed.
    Affected if HTTP services are exposed to untrusted networks (internet or DMZ)
  4. Review system logs for crashes
    Examine SAP system logs (work directory logs like dev_w*, st22 for ABAP dumps) and operating system logs (/var/log/messages, Windows Event Viewer) for recent null pointer dereference errors, kernel panics, or unexpected reboots that coincide with HTTP request patterns.
    Affected if Recent crashes or reboots have occurred with null pointer or kernel dereference errors in the logs
  5. Check ICM/HTTP logs for suspicious requests
    Review SAP ICM access logs (default location: /usr/sap/*/SYS/profile/icm*.log or via transaction SMICM) for unusual or malformed HTTP requests around the time of any incidents.
    Affected if Logs show malformed HTTP requests that could trigger the vulnerability, especially if crashes followed

If the system runs SAP NetWeaver AS for ABAP, is exposed to network HTTP traffic, and has experienced unexplained crashes with null pointer errors in the logs, it is likely affected by this vulnerability.

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 relevant SAP security patch when available. In the interim, consider implementing network-level filtering or a Web Application Firewall (WAF) to block potentially malicious HTTP requests targeting the affected SAP services.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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