CVE-2024-22257 json
Erroneous authentication pass in Spring Security
published 2024-03-18 2 y ago modified 2026-09-10 1 mo ago also GHSA-f3jh-qvm4-mg39 , EUVD-2024-0908
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
In Spring Security, versions 5.7.x prior to 5.7.12, 5.8.x prior to 5.8.11, versions 6.0.x prior to 6.0.9, versions 6.1.x prior to 6.1.8, versions 6.2.x prior to 6.2.3, an application is possible vulnerable to broken access control when it directly uses the AuthenticatedVoter#vote passing a null Authentication parameter.
Patch / fix
- maven org.springframework.security:spring-security-core 5.7.12, 5.8.11, 6.1.8, 6.2.3
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-22257 updated cvss 9.8
spring-security: Broken Access Control With Direct Use of AuthenticatedVoter
-
Red Hat OpenShift Developer Tools and Services jenkins Red Hat build of Apache Camel - HawtIO 4 spring-security spring-securityaffected: workaround, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
-
Red Hat build of Apache Camel for Spring Boot 3 spring-security spring-security Red Hat build of Apache Camel for Spring Boot 4 spring-security spring-security Red Hat Fuse 7 spring-security spring-security Red Hat OpenShift Container Platform 3.11 jenkins Red Hat OpenShift Dev Spaces devspaces/pluginregistry-rhel8affected: workaround, no fix available “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
-
Red Hat Process Automation 7 spring-security spring-securityaffected: workaround, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
-
Red Hat build of Apache Camel 3.20.6 for Spring Bootfixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3708
-
Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:4884
-
Red Hat Fuse 7.13.0fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2024:3354
-
Red Hat A-MQ Clients 2 spring-security spring-security Red Hat Build of Keycloak spring-security spring-security Red Hat Data Grid 8 spring-security spring-security Red Hat Integration Camel K 1 spring-security spring-security Red Hat JBoss Data Grid 7 spring-security spring-security Red Hat Single Sign-On 7 spring-security spring-securitynot affected: vulnerable code not present
+1 more productsfewer
Red Hat streams for Apache Kafka spring-security spring-security
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 23 mo ago
Exploit prediction
0.96% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
| GitHub | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.security:spring-security-core | <5.7.12 >=5.8.0, <5.8.11 >=6.0.0, <6.1.8 >=6.2.0, <6.2.3 |
5.7.12 5.8.11 6.1.8 6.2.3 |
Affected products
- N/A Spring Security
- pivotal_software spring_security
Classification
- Weakness
- Technology feeds
References
-
github.com
/spring-projects/spring-security/commit/5a7f12f1a9fdb4edaab6f61495f1d781a7273b61
web
-
spring.io
/security/cve-2024-22257
web
- security.netapp.com /advisory/ntap-20240419-0005/
- github.com /dependency-check/DependencyCheck/issues/8642
-
nvd.nist.gov
/vuln/detail/CVE-2024-22257
advisory
-
github.com
/spring-projects/spring-security
package
-
security.netapp.com
/advisory/ntap-20240419-0005
web
Sources
- CVE List CVE-2024-22257
- GitHub Advisory GHSA-f3jh-qvm4-mg39
- NVD CVE-2024-22257
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.