CVE-2018-2380
Published: November 3, 2021
Official Description
SAP Customer Relationship Management (CRM) contains a path traversal vulnerability that allows an attacker to exploit insufficient validation of path information provided by users.
CISA KEV Advisory
SAP Customer Relationship Management (CRM) Path Traversal Vulnerability
SAP Customer Relationship Management (CRM) contains a path traversal vulnerability that allows an attacker to exploit insufficient validation of path information provided by users.
Apply updates per vendor instructions.
Risk Analysis
SAP Customer Relationship Management (CRM) is vulnerable to a path traversal flaw due to insufficient validation of user-provided path information. The high EPSS score of 0.45533 indicates a significant likelihood of exploitation, and its presence in the KEV catalog confirms it has been actively exploited.
This vulnerability has been actively exploited in the wild and is listed in CISA's Known Exploited Vulnerabilities catalog. The nature of path traversal often allows for remote exploitation.
Apply all available security patches and updates for SAP CRM. Implement robust input validation for all user-supplied path information to prevent traversal attacks.
Technical Analysis
CVE-2018-2380 requires local access, meaning attackers must already have a foothold on the target system.
Exploitation requires some privileges, which limits the exposure to scenarios where an attacker has already gained initial access.
CISA has added CVE-2018-2380 to the Known Exploited Vulnerabilities (KEV) catalog, confirming active exploitation in the wild. U.S. federal agencies are required to patch this within the mandated timeframe, and all organizations should treat remediation as urgent.
Affected Vendors & Products
Exploit & PoC Resources
All References (1)
Quick Facts
Recommended Actions
- →Apply vendor patches immediately
- →Monitor CVE-2018-2380 in threat intel feeds
- →Review IDS/IPS signatures for exploitation attempts
- !CISA KEV: Federal agencies must patch per BOD 22-01 timeline
- !Active exploitation confirmed — treat as P1