CVE-2020-5410
VMware Tanzu Spring Cloud Config Directory Traversal Vulnerability
VMware Tanzu Spring Cloud Configuration (Config) Server
Spring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior to 2.1.9, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead to a directory traversal attack.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 25 March 2022. US federal agencies were required to remediate it by 15 April 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 95.6%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Frequently asked questions
Is CVE-2020-5410 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2020-5410.
What does CVE-2020-5410 affect?
CVE-2020-5410 affects VMware Tanzu Spring Cloud Configuration (Config) Server. Spring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior to 2.1.9, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead to a directory traversal attack.
How severe is CVE-2020-5410?
CVE-2020-5410 is rated HIGH with a CVSS base score of 7.5. EPSS puts the probability of exploitation in the next 30 days at 95.6%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 15 April 2022.
How should organisations respond to CVE-2020-5410?
Apply the vendor patch for VMware Tanzu Spring Cloud Configuration (Config) Server as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.