org.springframework.security:spring-security-core vulnerabilities
Spring Security
- Registry
- Maven
- Latest
- 7.1.2
- License
- Apache License, Version 2.0
31 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-core -DdepVersion=7.1.2 -DforceVersion=trueIs your project on an affected org.springframework.security:spring-security-core?
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-core
Spring Security Vulnerable to User Attribute Enumeration when Using DaoAuthenticationProvider
- Affected
- >=5.7.0 <=5.7.22 · >=5.8.0 <=5.8.24 · >=6.3.0 <=6.3.15 · >=6.4.0 <=6.4.15 · >=6.5.0 <6.5.10 · >=7.0.0 <7.0.5
- Fixed in
- 6.5.10, 7.0.5
Spring Security Core has a TOCTOU race condition when One-Time Token login with JdbcOneTimeTokenService is configured
- Affected
- >=6.5.0 <6.5.10 · >=7.0.3 <7.0.5 · >=6.4.0 <=6.4.13
- Fixed in
- 6.5.10, 7.0.5
Spring Security has a broken timing attack mitigation implemented in DaoAuthenticationProvide
- Affected
- >=6.3.8 <6.3.9 · >=6.4.4 <6.4.5
- Fixed in
- 6.3.9, 6.4.5
Spring Security annotation detection mechanism has authorization bypass
- Affected
- >=6.4.0 <6.4.10 · >=6.5.0 <6.5.4
- Fixed in
- 6.4.10, 6.5.4
Spring Security authorization bypass for method security annotations on private methods
- Affected
- >=6.4.0 <6.4.6
- Fixed in
- 6.4.6
Spring Security Vulnerable to Authorization Bypass via Security Annotations
- Affected
- >=6.4.0 <6.4.4
- Fixed in
- 6.4.4
Spring Framework has Authorization Bypass for Case Sensitive Comparisons
- Affected
- <5.7.14 · >=5.8.0 <5.8.16 · >=6.0.0 <6.0.14 · >=6.1.0 <6.1.12 · >=6.2.0 <6.2.8 · >=6.3.0 <6.3.5
- Fixed in
- 5.7.14, 5.8.16, 6.0.14, 6.1.12, 6.2.8, 6.3.5
Spring Security Missing Authorization vulnerability
- Affected
- >=6.3.0 <6.3.2
- Fixed in
- 6.3.2
Erroneous authentication pass in Spring Security
- Affected
- <5.7.12 · >=5.8.0 <5.8.11 · >=6.0.0 <6.1.8 · >=6.2.0 <6.2.3
- Fixed in
- 5.7.12, 5.8.11, 6.1.8, 6.2.3
Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated
- Affected
- >=6.1.0 <6.1.7 · >=6.2.0 <6.2.2
- Fixed in
- 6.1.7, 6.2.2
Spring Security logout not clearing security context
- Affected
- >=5.7.0 <5.7.8 · >=5.8.0 <5.8.3 · >=6.0.0 <6.0.3
- Fixed in
- 5.7.8, 5.8.3, 6.0.3
Spring Security authorization rules can be bypassed via forward or include dispatcher types
- Affected
- >=5.7.0 <5.7.5 · >=5.6.0 <5.6.9
- Fixed in
- 5.6.9, 5.7.5
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
Integer overflow in BCrypt class in Spring Security
- Affected
- >=5.2.0.RELEASE <5.5.7 · >=5.6.0 <5.6.4
- Fixed in
- 5.5.7, 5.6.4
Improper Control of Generation of Code in Spring Security
- Affected
- <2.0.7 · >=3.0.0 <3.0.6
- Fixed in
- 2.0.7, 3.0.6
Exposure of Sensitive Information to an Unauthorized Actor in Spring Security
- Affected
- <2.0.8 · >=3.0.0 <3.0.8 · >=3.1.0 <3.1.3
- Fixed in
- 2.0.8, 3.0.8, 3.1.3
Concurrent Execution using Shared Resource with Improper Synchronization in Spring Security
- Affected
- <2.0.7 · >=3.0.0 <3.0.6
- Fixed in
- 2.0.7, 3.0.6
Spring Framework and Spring Security vulnerable to Deserialization of Untrusted Data
- Affected
- >=3.0.0 <3.0.6 · >=2.0.0 <2.0.7
- Fixed in
- 2.0.7, 3.0.6
Authentication Bypass Using an Alternate Path or Channel in SpringSource Spring Security and Acegi Security
- Affected
- >=2.0.0 <2.0.6 · >=3.0.0 <3.0.4
- Fixed in
- 2.0.6, 3.0.4
Deserialization of Untrusted Data in Spring Security
- Affected
- >=4.2.0.RELEASE <4.2.3.RELEASE · >=5.0.0.M1 <5.0.0.M2
- Fixed in
- 4.2.3.RELEASE, 5.0.0.M2
Improper Authentication in Spring Security
- Affected
- >=3.2.0 <3.2.2.RELEASE · >=3.1.0 <3.1.5.RELEASE
- Fixed in
- 3.1.5.RELEASE, 3.2.2.RELEASE
Resource Exhaustion in Spring Security
- Affected
- >=5.5.0 <5.5.1 · >=5.4.0 <5.4.7 · >=5.3.0 <5.3.10 · >=5.2.0 <5.2.11
- Fixed in
- 5.2.11, 5.3.10, 5.4.7, 5.5.1
Security Constraint Bypass in Spring Security
- Affected
- <3.2.10.RELEASE · >=4.0.0.RELEASE <4.1.4.RELEASE · >=4.2.0.RELEASE <4.2.1.RELEASE
- Fixed in
- 3.2.10.RELEASE, 4.1.4.RELEASE, 4.2.1.RELEASE
Authorization Bypass in Spring Security
- Affected
- <3.1.7 · >=3.2.0 <3.2.5
- Fixed in
- 3.1.7, 3.2.5
Insufficient Entropy in Spring Security
- Affected
- >=5.3.0 <5.3.2 · >=5.2.0 <5.2.4 · >=5.1.0 <5.1.10 · >=5.0.0 <5.0.16 · <4.2.16
- Fixed in
- 4.2.16, 5.0.16, 5.1.10, 5.2.4, 5.3.2
Signature wrapping vulnerability in Spring Security
- Affected
- >=5.2.0 <5.2.4 · >=5.3.0 <5.3.2
- Fixed in
- 5.2.4, 5.3.2
Insufficiently Protected Credentials and Improper Authentication in Spring Security
- Affected
- <4.2.13
- Fixed in
- 4.2.13
Spring Security uses insufficiently random values
- Affected
- >=4.2.0 <4.2.12 · >=5.0.0 <5.0.12 · >=5.1.0 <5.1.5
- Fixed in
- 4.2.12, 5.0.12, 5.1.5
Spring Security vulnerable to Authorization Bypass
- Affected
- >=5.1.0 <5.1.2
- Fixed in
- 5.1.2
Spring Security and Spring Framework may not recognize certain paths that should be protected
- Affected
- <4.1.1
- Fixed in
- 4.1.1
Improper Input Validation in org.springframework.security:spring-security-core, org.springframework.security:spring-security-core , and org.springframework:spring-core
- Affected
- >=4.2.0 <4.2.4 · >=5.0.0 <5.0.1 · >=4.1.0 <4.1.5
- Fixed in
- 4.1.5, 4.2.4, 5.0.1
Is your org.springframework.security:spring-security-core version vulnerable?
- org.springframework.security:spring-security-core 7.1No known advisories in 7.1.2
- org.springframework.security:spring-security-core 7.0No known advisories in 7.0.8
- org.springframework.security:spring-security-core 6.5No known advisories in 6.5.11
- org.springframework.security:spring-security-core 6.42 advisories in 6.4.13
- org.springframework.security:spring-security-core 6.31 advisory in 6.3.10
- org.springframework.security:spring-security-core 6.2No known advisories in 6.2.8
- org.springframework.security:spring-security-core 6.11 advisory in 6.1.9
- org.springframework.security:spring-security-core 6.02 advisories in 6.0.8
- org.springframework.security:spring-security-core 5.81 advisory in 5.8.16
- org.springframework.security:spring-security-core 5.71 advisory in 5.7.14
- org.springframework.security:spring-security-core 5.62 advisories in 5.6.12
- org.springframework.security:spring-security-core 5.52 advisories in 5.5.8
- org.springframework.security:spring-security-core 5.43 advisories in 5.4.11
- org.springframework.security:spring-security-core 5.34 advisories in 5.3.13
Which of your client projects still run an old org.springframework.security:spring-security-core?
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.