# CVE-2020-5405: Directory Traversal with spring-cloud-config-server

> Attackers can read arbitrary configuration files via directory traversal in Spring Cloud Config Server, exposing sensitive data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Mar 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-g86w-v5vg-9gxf

## What is CVE-2020-5405?

CVE-2020-5405 is a medium-severity path traversal vulnerability in Spring Cloud Config, published on 5 Mar 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Spring Cloud Config, versions 2.2.x prior to 2.2.2, versions 2.1.x prior to 2.1.7, 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 a directory traversal attack.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2020-5405?

4 open source packages ship an affected version, including org.springframework.cloud:spring-cloud-config-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.cloud:spring-cloud-config-server` | Maven | From 2.1.0 | 2.1.7 |
| `org.springframework.cloud:spring-cloud-config-server` | Maven | From 2.1.0 | 2.1.7 |
| `org.springframework.cloud:spring-cloud-config-server` | Maven | From 2.2.0 | 2.2.2 |
| `org.springframework.cloud:spring-cloud-config-server` | Maven | From 2.2.0 | 2.2.2 |

Products: Vmware Spring Cloud Config.

## How do I fix CVE-2020-5405?

Upgrade org.springframework.cloud:spring-cloud-config-server to a fixed version for your release line: 2.1.7 or 2.2.2.

## Is CVE-2020-5405 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-5405 exists.

Public exploit code:

- https://github.com/shoucheng3/spring-cloud__spring-cloud-config_CVE-2020-5405_2-1-6-RELEASE (github_poc): https://github.com/shoucheng3/spring-cloud__spring-cloud-config_CVE-2020-5405_2-1-6-RELEASE
- Spring Cloud Config - Local File Inclusion (nuclei): http/cves/2020/CVE-2020-5405.yaml

## Other vulnerabilities in Spring Cloud Config

- [CVE-2020-5410](https://insights.sbomify.com/CVE-2020-5410/): VMware Tanzu Spring Cloud Config Directory Traversal (high 7.5, exploited in the wild)
- [CVE-2026-40982](https://insights.sbomify.com/CVE-2026-40982/): Spring Cloud Config vulnerable to Path Traversal (critical 9.1)
- [CVE-2026-22739](https://insights.sbomify.com/CVE-2026-22739/): Spring Cloud Config Profile Substitution Can Allow Unintended Access To Files And Enable SSRF Attacks (high 8.6)
- [CVE-2026-40981](https://insights.sbomify.com/CVE-2026-40981/): Spring Cloud Config has an Authorization Bypass Through User-Controlled Key (high 7.5)
- [CVE-2026-41002](https://insights.sbomify.com/CVE-2026-41002/): Spring Cloud Config Server Susceptible To TOCTOU Attack (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-5405 and fix it if it is affected.

What it is: CVE-2020-5405 is a medium-severity path traversal vulnerability in Spring Cloud Config, published on 5 Mar 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-5405 exists.

Affected packages and fixed versions:
- org.springframework.cloud:spring-cloud-config-server (Maven): affected from 2.1.0; fixed in 2.1.7
- org.springframework.cloud:spring-cloud-config-server (Maven): affected from 2.1.0; fixed in 2.1.7
- org.springframework.cloud:spring-cloud-config-server (Maven): affected from 2.2.0; fixed in 2.2.2
- org.springframework.cloud:spring-cloud-config-server (Maven): affected from 2.2.0; fixed in 2.2.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-5405/ (Markdown: https://insights.sbomify.com/CVE-2020-5405/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-5405
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-5405
- OSV: https://osv.dev/vulnerability/CVE-2020-5405

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-5405/
Summaries are generated and may contain mistakes; the official description above is the record.