CVE-2020-5410 — spring-cloud-config-server
HIGHCVE-2020-5410 is a high-severity (CVSS 7.5) CWE-23 vulnerability in org.springframework.cloud:spring-cloud-config-server. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-03-25) — treat it as actively exploited and patch now. A fix is available for org.springframework.cloud:spring-cloud-config-server — see the affected versions and patch details below.
Directory traversal attack in Spring Cloud Config
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-03-25. Federal agencies were required to remediate by 2022-04-15.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2020-5410.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-5410 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).
Where this sits among everything scored
Of 394,415 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.cloud:spring-cloud-config-server | ≥ 2.1.0&&< 2.1.9 | 2.1.9org.springframework.cloud:spring-cloud-config-server:2.1.9 |
| ☕Maven | org.springframework.cloud:spring-cloud-config-server | ≥ 2.2.0&&< 2.2.3 | 2.2.3org.springframework.cloud:spring-cloud-config-server:2.2.3 |
Affected Products
spring cloud configvmwareResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Spring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior…
Spring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior…
Spring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior…
Spring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior…
Spring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior…
Spring Cloud Config, versions 2.2.x prior to 2.2.3, versions 2.1.x prior…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.cloud:spring-cloud-config-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.cloud:spring-cloud-config-server to 2.1.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-5410 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
How to detect CVE-2020-5410
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2020-5410 -u https://target- Template
- Spring Cloud Config Server - Local File Inclusion
- Severity
- high
- Impact
- An attacker can exploit this vulnerability to read arbitrary files from the server, potentially leading to unauthorized access or sensitive information disclosure.
- Remediation
- Upgrade to a patched version of Spring Cloud Config Server or apply the recommended security patches.
Template by ProjectDiscovery nuclei-templates (mavericknerd), MIT licensed. View the full template. Scan only systems you are authorised to test.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Users of vulnerable versions or older, unsupported versions of spring-cloud-config-server should upgrade to a patched version. Spring-cloud-config-server should only be accessible on internal networks.Source: Red Hat security advisory for CVE-2020-5410 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Fuse 7.8.0 | see advisory | RHSA-2020:5568 |
| Red Hat Fuse 7.9 | spring-cloud-config-server | RHSA-2021:3140 |
Frequently Asked Questions
Is CVE-2020-5410 in your dependencies?
Find it across Maven, including transitive dependencies.