org.springframework.security:spring-security-web vulnerabilities
Spring Security
- Registry
- Maven
- Latest
- 7.1.2
- License
- Apache License, Version 2.0
7 known advisories
The latest version, 7.1.2, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.springframework.security:spring-security-web -DdepVersion=7.1.2 -DforceVersion=trueIs your project on an affected org.springframework.security:spring-security-web?
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.security:spring-security-web
Spring Security Vulnerable to Unauthorized User Impersonation when Using X.509 Client Certificates
- Affected
- >=6.5.0 <6.5.11 · >=6.4.0 <=6.4.13 · >=6.0.0 <=6.3.10 · >=5.8.0 <=5.8.16 · <=5.7.14
- Fixed in
- 6.5.11
Spring Security: Open Redirect via Unvalidated Post-Login Redirect URL Stored in CookieRequestCache
- Affected
- >=7.0.0 <7.0.6 · >=6.5.0 <6.5.11 · >=6.3.0 <=6.3.16 · >=5.8.0 <=5.8.25 · <=5.7.23
- Fixed in
- 6.5.11, 7.0.6
Spring Security Vulnerable to Unauthorized User Impersonation when Using X.509 Client Certificates
- Affected
- >=7.0.0 <7.0.5
- Fixed in
- 7.0.5
Spring Security HTTP Headers Are not Written Under Some Conditions
- Affected
- <=5.7.14 · >=5.8.0 <=5.8.16 · >=6.0.0 <=6.3.10 · >=6.4.0 <=6.4.13 · >=6.5.0 <6.5.9 · >=7.0.0 <7.0.4
- Fixed in
- 6.5.9, 7.0.4
Spring Security vulnerable to Authorization Bypass of Static Resources in WebFlux Applications
- Affected
- >=5.0.0 <5.7.13 · >=5.8.0 <5.8.15 · >=6.2.0 <6.2.7 · >=6.0.0 <6.0.13 · >=6.1.0 <6.1.11 · >=6.3.0 <6.3.4
- Fixed in
- 5.7.13, 5.8.15, 6.0.13, 6.1.11, 6.2.7, 6.3.4
Authorization bypass in Spring Security
- Affected
- >=5.5.0 <5.5.7 · >=5.6.0 <5.6.4 · <5.4.11
- Fixed in
- 5.4.11, 5.5.7, 5.6.4
Privilege escalation in spring security
- Affected
- >=5.4.0 <5.4.4 · >=5.3.0 <5.3.8 · <5.2.9
- Fixed in
- 5.2.9, 5.3.8, 5.4.4
Is your org.springframework.security:spring-security-web version vulnerable?
- org.springframework.security:spring-security-web 7.1No known advisories in 7.1.2
- org.springframework.security:spring-security-web 7.0No known advisories in 7.0.8
- org.springframework.security:spring-security-web 6.5No known advisories in 6.5.11
- org.springframework.security:spring-security-web 6.42 advisories in 6.4.13
- org.springframework.security:spring-security-web 6.33 advisories in 6.3.10
- org.springframework.security:spring-security-web 6.22 advisories in 6.2.8
- org.springframework.security:spring-security-web 6.13 advisories in 6.1.9
- org.springframework.security:spring-security-web 6.03 advisories in 6.0.8
- org.springframework.security:spring-security-web 5.83 advisories in 5.8.16
- org.springframework.security:spring-security-web 5.73 advisories in 5.7.14
- org.springframework.security:spring-security-web 5.64 advisories in 5.6.12
- org.springframework.security:spring-security-web 5.54 advisories in 5.5.8
- org.springframework.security:spring-security-web 5.44 advisories in 5.4.11
- org.springframework.security:spring-security-web 5.35 advisories in 5.3.13
Which of your client projects still run an old org.springframework.security:spring-security-web?
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.