CVE-2020-5410
VMware Tanzu Spring Cloud Config Directory Traversal
- Published2 Jun 2020
- Added to CISA KEV25 Mar 2022
- Remediation due15 Apr 2022
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2020-5410 being actively exploited?
Yes. CVE-2020-5410 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 25 Mar 2022.
How severe is CVE-2020-5410?
CVE-2020-5410 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 95.6% probability of exploitation.
Which products are affected by CVE-2020-5410?
Affected products include VMware Spring Cloud Config.
How do I fix CVE-2020-5410?
Upgrade affected software to a fixed version, for example VMware Spring Cloud Config 2.1.9 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2020-5410 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.