Spring Cloud Config vulnerable to Path Traversal
Spring Cloud Config
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.cloud:spring-cloud-config-server Maven |
|
|
Spring Cloud Config
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.cloud:spring-cloud-config-server Maven |
|
|
Spring Cloud Config allows applications to serve arbitrary text and binary 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. Spring Cloud Config 3.1.x: affected from 3.1.0 through 3.1.13 (inclusive); upgrade to 3.1.14 or greater (Enterprise Support Only). Spring Cloud Config 4.1.x: affected from 4.1.0 through 4.1.9 (inclusive); upgrade to 4.1.10 or greater (Enterprise Support Only). Spring Cloud Config 4.2.x: affected from 4.2.0 through 4.2.6 (inclusive); upgrade to 4.2.7 or greater (Enterprise Support Only). Spring Cloud Config 4.3.x: affected from 4.3.0 through 4.3.2 (inclusive); upgrade to 4.3.3 or greater. Spring Cloud Config 5.0.x: affected from 5.0.0 through 5.0.2 (inclusive); upgrade to 5.0.3 or greater.
From the CVE record · vmware
The spring-cloud-config-server module is vulnerable to directory traversal through a specially crafted URL. An attacker can trigger it by sending a request to the server; the input does not specify whether authentication or user interaction is required.
Teams running Spring Cloud Config Server should check versions 3.1.0–3.1.13, 4.1.0–4.1.9, 4.2.0–4.2.6, 4.3.0–4.3.2, and 5.0.0–5.0.2.