org.springframework.cloud:spring-cloud-config-server vulnerabilities
spring-cloud-config-server
- Registry
- Maven
- Latest
- 5.0.6
- License
- Apache License, Version 2.0
8 known advisories
The latest version, 5.0.6, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.springframework.cloud:spring-cloud-config-server -DdepVersion=5.0.6 -DforceVersion=trueIs your project on an affected org.springframework.cloud:spring-cloud-config-server?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.springframework.cloud:spring-cloud-config-server
Spring Cloud Config vulnerable to Path Traversal
- Affected
- <=3.1.13 · >=4.1.0 <=4.1.9 · >=4.2.0 <=4.2.6 · >=4.3.0 <4.3.3 · >=5.0.0 <5.0.3
- Fixed in
- 4.3.3, 5.0.3
Spring Cloud Config has an Authorization Bypass Through User-Controlled Key
- Affected
- >=3.1.0 <=3.1.13 · >=4.1.0 <=4.1.9 · >=4.2.0 <=4.2.6 · >=4.3.0 <4.3.3 · >=5.0.0 <5.0.3
- Fixed in
- 4.3.3, 5.0.3
Spring Cloud Config Server Susceptible To TOCTOU Attack
- Affected
- >=3.1.0 <=3.1.13 · >=4.1.0 <=4.1.9 · >=4.2.0 <=4.2.6 · >=4.3.0 <4.3.3 · >=5.0.0 <5.0.3 · >=3.0.0 <=3.0.7
- Fixed in
- 4.3.3, 5.0.3
Spring Cloud Config Server Logged Sensitive Information
- Affected
- >=3.1.0 <=3.1.13 · >=4.1.0 <=4.1.9 · >=4.2.0 <=4.2.6 · >=4.3.0 <4.3.3 · >=5.0.0 <5.0.3 · >=3.0.0 <=3.0.7
- Fixed in
- 4.3.3, 5.0.3
Spring Cloud Config Server: Path Traversal via Profile Parameter Allows Arbitrary File Access
- Affected
- >=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 · <=3.1.10
- Fixed in
- 4.3.2, 5.0.2
Directory traversal attack in Spring Cloud Config
- Affected
- >=2.1.0 <2.1.9 · >=2.2.0 <2.2.3
- Fixed in
- 2.1.9, 2.2.3
Directory traversal attack in Spring Cloud Config
- Affected
- >=2.1.0 <2.1.7 · >=2.2.0 <2.2.2
- Fixed in
- 2.1.7, 2.2.2
Path Traversal in Spring Cloud Config
- Affected
- <1.4.6 · >=2.0.0 <2.0.4 · >=2.1.0 <2.1.2
- Fixed in
- 1.4.6, 2.0.4, 2.1.2
Is your org.springframework.cloud:spring-cloud-config-server version vulnerable?
- org.springframework.cloud:spring-cloud-config-server 5.0No known advisories in 5.0.6
- org.springframework.cloud:spring-cloud-config-server 4.3No known advisories in 4.3.4
- org.springframework.cloud:spring-cloud-config-server 4.25 advisories in 4.2.4
- org.springframework.cloud:spring-cloud-config-server 4.15 advisories in 4.1.7
- org.springframework.cloud:spring-cloud-config-server 4.01 advisory in 4.0.5
- org.springframework.cloud:spring-cloud-config-server 3.15 advisories in 3.1.10
- org.springframework.cloud:spring-cloud-config-server 3.04 advisories in 3.0.7
Which of your client projects still run an old org.springframework.cloud:spring-cloud-config-server?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.