dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2024-54197

HIGH · 7.2 CVSS v3.1 Published 2024-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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 Administrator(System Overview) allows an authenticated attacker to enumerate accessible HTTP endpoints in the internal network by specially crafting HTTP requests. On successful exploitation this can result in Server-Side Request Forgery (SSRF) which could have a low impact on integrity and confidentiality of data. It has no impact on availability of the application.

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

SAP NetWeaver Administrator's System Overview component contains a Server-Side Request Forgery (SSRF) vulnerability that allows authenticated attackers to make the server enumerate accessible HTTP endpoints in the internal network. By crafting malicious HTTP requests, an attacker can probe internal infrastructure, potentially accessing sensitive internal services and data that should not be externally reachable.

MitigationApply the relevant SAP security patch for CVE-2024-54197. Additionally, implement network segmentation and restrict internal endpoint access to prevent the server from making arbitrary requests to internal resources.

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
Low
Integrity
Low
Availability
None

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

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 SAP NetWeaver installation and version
    Locate the SAP NetWeaver installation directory and check the version information using SAP tools like SAPMMC, SAP Version Info, or by querying the SAP system via transaction code SM51 or using the SAP NetWeaver Administrator web interface.
    Affected if The installed SAP NetWeaver version matches the vulnerable version range listed in the official SAP security note for CVE-2024-54197.
  2. Confirm SAP NetWeaver Administrator (NWA) is accessible
    Verify that the SAP NetWeaver Administrator web interface is reachable by accessing the NWA URLs (typically at /nwa on the SAP Java stack). Check if the System Overview functionality is available under the NWA navigation.
    Affected if The NWA interface and System Overview component are accessible and operational on the affected system.
  3. Check authentication status for NWA access
    Review the authentication configuration for the SAP NetWeaver Administrator to confirm whether it requires valid credentials for access. Verify that the vulnerability requires an authenticated attacker.
    Affected if NWA is accessible with valid credentials, confirming the authentication requirement for exploitation.
  4. Assess network exposure of NWA interface
    Determine if the NWA web interface is exposed to untrusted networks by reviewing firewall rules, load balancer configurations, and reverse proxy settings that control access to the NWA URLs.
    Affected if The NWA interface is reachable from networks outside the trusted internal network, allowing potential attackers to authenticate and exploit the SSRF vulnerability.

A user is affected if they are running a vulnerable SAP NetWeaver version with the NWA System Overview component accessible from a network where untrusted users can authenticate and send crafted HTTP requests.

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 for CVE-2024-54197. Additionally, implement network segmentation and restrict internal endpoint access to prevent the server from making arbitrary requests to internal resources.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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