dbcve.org
SaptmuiApplication · Sap

CVE-2024-37171

MEDIUM · 5.0 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 →
56/100
Remediation priority · Elevated
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
SAP Transportation Management (Collaboration Portal) allows an attacker with non-administrative privileges to send a crafted request from a vulnerable web application. This will trigger the application handler to send a request to an unintended service, which may reveal information about that service. The information obtained could be used to target internal systems behind firewalls that are normally inaccessible to an attacker from the external network, resulting in a Server-Side Request Forgery vulnerability. There is no effect on integrity or 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 · high confidence

SAP Transportation Management Collaboration Portal contains a Server-Side Request Forgery (SSRF) vulnerability allowing authenticated non-privileged users to craft requests that cause the application server to make arbitrary HTTP requests to internal or external services. This can expose information about internal systems behind firewalls that would normally be inaccessible from external networks.

MitigationApply the relevant SAP Security Note for this vulnerability (check SAP Support Portal for CVE-2024-37171). Additionally, implement network segmentation and restrict outbound connections from the application server to internal resources.

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
SaptmuiApplication
Affected:= 140= 150= 160= 170
Transportation ManagementApplication
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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 Transportation Management Collaboration Portal installation
    Locate the SAP Transport Management UI (SAPTUI) component on your system. Check for the presence of the SAP TMW (Transportation Management) web application server and its Collaboration Portal module. This is typically found in the SAP system directory under the SAP_TMW component or as a separate web application.
    Affected if The Collaboration Portal module of SAP Transportation Management is installed and running on the system.
  2. Verify Sap Saptmui version
    Check the installed version of the Sap Saptmui component. This can typically be found in the SAP system information transaction (SM37), in the software deployment manager, or by querying the SAP system version information for the TMW component. Compare your version against: 140, 150, 160, or 170.
    Affected if The installed Sap Saptmui version is exactly 140, 150, 160, or 170.
  3. Confirm authenticated user access to Collaboration Portal
    Verify that the Collaboration Portal functionality is accessible to authenticated users. Check the SAP user role assignments and ensure that non-privileged users have access to the Transportation Management Collaboration Portal interface. This can be verified through transaction SU01 or by reviewing the role configuration for TMW user roles.
    Affected if Non-privileged authenticated users can access the Collaboration Portal interface in SAP Transportation Management.
  4. Inspect outbound HTTP request capabilities
    Review the server configuration and logs for the ability to trigger outbound HTTP requests from the application server. Check if there are any URL-fetching or HTTP request features exposed through the Collaboration Portal that allow users to specify target URLs. Examine SAP transaction logs (SM37) and HTTP access logs for unusual outbound connection patterns.
    Affected if The Collaboration Portal allows authenticated users to trigger HTTP requests from the server to arbitrary URLs.

Your environment is affected if you have SAP Transportation Management with the Collaboration Portal running and accessible to authenticated users, particularly if the Sap Saptmui component version is 140, 150, 160, or 170.

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 Note for this vulnerability (check SAP Support Portal for CVE-2024-37171). Additionally, implement network segmentation and restrict outbound connections from the application server to internal resources.

Fix this in Saptmui 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-37171 — 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-37171 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