dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022. Known ransomware use
Customer Relationship ManagementApplication · Sap

CVE-2018-2380

MEDIUM · 6.6 CVSS v3.1 Published 2018-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware Public exploit 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 CRM, 7.01, 7.02,7.30, 7.31, 7.33, 7.54, allows an attacker to exploit insufficient validation of path information provided by users, thus characters representing "traverse to parent directory" are passed through to the file APIs.

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 CRM contains a path traversal vulnerability where insufficient validation of user-supplied path input allows directory traversal characters (such as '../') to be passed through to file APIs. This could allow an authenticated attacker to access files outside the intended document root directory.

MitigationImplement strict input validation and sanitization for all file path parameters, using allowlist validation and rejecting any path containing traversal sequences. Ensure file operations are restricted to intended directories.

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 ManagementApplication
Affected:= 7.01= 7.02= 7.30= 7.31= 7.33= 7.54

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/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 SAP CRM version
    Check the SAP CRM installed version by accessing the SAP system landscape directory (SLD), using transaction code SM37 to view system version, or checking the SAP CRM about screen via the web interface at /sap/public/about (if accessible). Compare the installed version to the affected list: 7.01, 7.02, 7.30, 7.33, or 7.54.
    Affected if The installed version matches exactly 7.01, 7.02, 7.30, 7.33, or 7.54.
  2. Confirm web component exposure
    Determine if the SAP CRM web client or IC WebClient is enabled and accessible. Check via transaction SICF or by attempting to access the standard SAP CRM web URLs such as /sap/bc/bsp/sap/crm_ui_frame or /sap/crm. Verify whether the ICM (Internet Communication Manager) is configured to expose CRM services.
    Affected if The SAP CRM web components are active and externally or internally accessible.
  3. Verify path handling in CRM web services
    Review the configuration of SAP CRM web services that handle file or document requests. Use transaction SE80 or SE24 to inspect the BSP (Business Server Pages) applications and their handling of path parameters. Check if any custom BSP applications or standard CRM components accept path-like parameters without proper validation.
    Affected if Any CRM web service or BSP application accepts user-controlled path parameters that could contain directory traversal sequences.
  4. Audit input validation settings
    Examine SAP CRM security configuration for input validation. Use transaction SM30 to view table entries related to validation (e.g., view V_TADIR for repository objects). Check whether custom validation exists for path-related parameters in the CRM application layer, particularly in IC WebClient components.
    Affected if No custom input validation or allowlist filtering is implemented for path parameters in the affected CRM components.

A system is affected if SAP CRM versions 7.01, 7.02, 7.30, 7.33, or 7.54 are installed with the web client or IC WebClient enabled and path parameters are accepted without validation.

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

Implement strict input validation and sanitization for all file path parameters, using allowlist validation and rejecting any path containing traversal sequences. Ensure file operations are restricted to intended directories.

Fix this in Customer Relationship Management Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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