dbcve.org
Customer Relationship Management S4fndApplication · Sap

CVE-2024-37173

MEDIUM · 6.1 CVSS v3.1 Published 2024-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Due to insufficient input validation, SAP CRM WebClient UI allows an unauthenticated attacker to craft a URL link which embeds a malicious script. When a victim clicks on this link, the script will be executed in the victim's browser giving the attacker the ability to access and/or modify information with no effect 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

This is a reflected Cross-Site Scripting (XSS) vulnerability in SAP CRM WebClient UI where insufficient input validation allows an unauthenticated attacker to embed malicious JavaScript in a crafted URL. When a victim clicks the malicious link, the script executes in their browser context, enabling the attacker to access or modify information within the application.

MitigationApply the SAP security patch for CVE-2024-37173 when available. Users should avoid clicking untrusted links. Consider implementing web application firewall rules to detect and block XSS payloads in URL parameters as a temporary mitigation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Customer Relationship Management S4fndApplication
Affected:= 102= 103= 104= 105= 106= 107= 108
Customer Relationship Management Webclient UiApplication
Affected:= 701= 731= 746= 747= 748= 800= 801

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 CRM WebClient UI installation
    Check if the SAP CRM WebClient UI component is installed by querying the SAP system via transaction code SM37 or checking for the presence of BSP application /CRM/BSP_START or via SAP MII diagnostics
    Affected if The component is not installed means not affected; if installed, continue to version check
  2. Determine WebClient UI version
    In SAP system, use transaction code SPAM to check package version, or query table CRMD_ORDER via SE16 for the component version, or use transaction code SICF to check active services related to WebClient UI
    Affected if Installed version matches: 701, 731, 746, 747, 748, 800, or 801 in the Webclient Ui component
  3. Check S4FND component version
    Query SAP table CVERS or use transaction code SPAM to view installed software component versions for S4FND (SAP CRM foundation)
    Affected if Installed version matches: 102, 103, 104, 105, 106, 107, or 108 in S4fnd component
  4. Assess network exposure
    Verify if SAP CRM WebClient UI is accessible from external networks by reviewing ICM/Internet Communication Manager configuration (transaction SMICM) and firewall rules
    Affected if WebClient UI is exposed to untrusted networks increases risk of unauthenticated XSS exploitation
  5. Review web logs for XSS indicators
    Search SAP ICM trace files or HTTP access logs (transaction SMICM -> Goto -> Trace File -> icm_access_log) for URL parameters containing script tags, javascript:, or HTML tags in requests to /sap/bc/bsp URLs
    Affected if Suspicious crafted URLs with XSS payloads are found in logs targeting the WebClient UI

System is potentially affected if SAP CRM WebClient UI is installed and the version matches 701, 731, 746, 747, 748, 800, or 801 for Webclient Ui component OR version 102-108 for S4FND component, especially if exposed to untrusted network access.

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 SAP security patch for CVE-2024-37173 when available. Users should avoid clicking untrusted links. Consider implementing web application firewall rules to detect and block XSS payloads in URL parameters as a temporary mitigation.

Fix this in Customer Relationship Management S4fnd Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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