CVE-2020-5405 is a directory traversal vulnerability in the spring-cloud-config-server module of Spring Cloud Config. Affected versions allow attacker-controlled request components to influence the path used to resolve configuration resources, enabling retrieval of arbitrary configuration files via specially crafted URLs. The provided analysis indicates the vulnerable flow passes user-controlled name and label values through EnvironmentController into NativeEnvironmentRepository, where resource locations are constructed and later accessed through resource-loading logic that ultimately uses URL-based access. The exploitation technique relies on crafted path elements and normalization behavior, including use of the '(_)' placeholder that is converted to '/' during normalization, allowing traversal sequences to be introduced. The issue affects Spring Cloud Config 2.2.x prior to 2.2.2, 2.1.x prior to 2.1.7, and older unsupported versions, according to the CVE description provided in the content.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.