Spring Cloud Config Profile Substitution Can Allow Unintended Access To Files And Enable SSRF Attacks
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.1.13, 4.1.9, 4.2.3, 4.3.2, 5.0.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 Nuclei template
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
Vulnerability in Spring Cloud when substituting the profile parameter from a request made to the Spring Cloud Config Server configured to the native file system as a backend, because it was possible to access files outside of the configured search directories.This issue affects Spring Cloud: from 3.1.X before 3.1.13, from 4.1.X before 4.1.9, from 4.2.X before 4.2.3, from 4.3.X before 4.3.2, from 5.0.X before 5.0.2.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Spring Spring Cloud
From 3.1.x · fixed in 3.1.13; From 4.1.x · fixed in 4.1.9; From 4.2.x · fixed in 4.2.3; From 4.3.x · fixed in 4.3.2; From 5.0.x · fixed in 5.0.2
- org.springframework.cloud:spring-cloud-config-serverMaven
From 4.3.0 · fixed in 4.3.2
- org.springframework.cloud:spring-cloud-config-serverMaven
From 5.0.0-M1 · fixed in 5.0.2
- org.springframework.cloud:spring-cloud-config-serverMaven
From 4.2.0 · through 4.2.4
- org.springframework.cloud:spring-cloud-config-serverMaven
From 4.0.0 · through 4.1.7
- org.springframework.cloud:spring-cloud-config-serverMaven
through 3.1.10