Spring Cloud Config Profile Substitution Can Allow Unintended Access To Files And Enable SSRF Attacks
Spring Cloud
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.cloud:spring-cloud-config-server Maven |
|
|
Spring Cloud
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.cloud:spring-cloud-config-server Maven |
|
|
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.
From the CVE record · vmware
Spring Cloud Config Server is vulnerable when it uses the native file system backend. An attacker can use the profile parameter in a request to access files outside the configured search directories. The input does not specify whether authentication or user interaction is required.
Teams running Maven package org.springframework.cloud:spring-cloud-config-server in the listed affected ranges should check their deployments: >=4.3.0 <4.3.2, >=5.0.0-M1 <5.0.2, >=4.2.0 <=4.2.4, >=4.0.0 <=4.1.7, or <=3.1.10.