cve.bz

CVE-2024-22234 vmware spring security: Improper Access Control

7.4 highEPSS 0.7%Fix available

High (7.4) in vmware spring security. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.security:spring-security-core 6.1.7, 6.2.2.

On this page
In Spring Security, versions 6.1.x prior to 6.1.7 and versions 6.2.x prior to 6.2.2, an application is vulnerable to broken access control when it directly uses the AuthenticationTrustResolver.isFullyAuthenticated(Authentication) method. Specifically, an application is vulnerable if: * The application uses AuthenticationTrustResolver.isFullyAuthenticated(Authentication) directly and a null authentication parameter is passed to it resulting in an erroneous true return value. An application is not vulnerable if any of the following is true: * The application does not use AuthenticationTrustResolver.isFullyAuthenticated(Authentication) directly. * The application does not pass null to AuthenticationTrustResolver.isFullyAuthenticated * The application only uses isFullyAuthenticated via Method Security https://docs.spring.io/spring-security/reference/servlet/authorization/method-security.html  or HTTP Request Security https://docs.spring.io/spring-security/reference/servlet/authorization/authorize-http-requests.html

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 53rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2024-02-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-22234 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-22234?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-22234?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-22234 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring Securityfrom 6.1.x before 6.1.7
Spring Securityfrom 6.2.x before 6.2.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-w3w6-26f2-p474Mavenorg.springframework.security:spring-security-core>=6.1.0 <6.1.76.1.7
GHSA-w3w6-26f2-p474Mavenorg.springframework.security:spring-security-core>=6.2.0 <6.2.26.2.2

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat considers this as a Moderate impact since it requires the malicious user to have knowledge of how a server implements the authentication resolver from Spring Security. A validation is also suggested to make sure there are no null parameters and no erroneous true is triggered from this method.

An application is not vulnerable if any of the following are true:

- The application does not use AuthenticationTrustResolver.isFullyAuthenticated(Authentication) directly

- The application does not pass null to AuthenticationTrustResolver.isFullyAuthenticated

- The application only uses isFullyAuthenticated via Method Security or HTTP Request Security

Red Hat's mitigation

Make sure the application is not vulnerable according to the description bullet points mentioned in this page.

ProductPackageStateAdvisory
HawtIO 4.0.0 for Red Hat build of Apache Camel 4spring-securityFixed 2024-06-03RHSA-2024:3550
Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2Fixed 2024-07-25RHSA-2024:4884
Red Hat OpenShift Dev Spaces 3 Containersdevspaces/pluginregistry-rhel8:3.16-16Fixed 2024-09-12RHSA-2024:6667
A-MQ Clients 2spring-securityNot affected
OpenShift Developer Tools and ServicesjenkinsWill not fix
Red Hat build of Apache Camel for Spring Boot 3spring-securityNot affected
Red Hat build of Apache Camel for Spring Boot 4spring-securityAffected
Red Hat build of Apache Camel - HawtIO 4spring-securityNot affected
Red Hat Build of Keycloakspring-securityNot affected
Red Hat build of Quarkusquarkus-spring-securityNot affected
Red Hat Data Grid 8spring-securityNot affected
Red Hat Decision Manager 7spring-securityOut of support scope
Red Hat Enterprise Linux 8log4j:2/log4jNot affected
Red Hat Enterprise Linux 9log4jNot affected
Red Hat Fuse 7spring-securityOut of support scope
Red Hat Integration Camel K 1spring-securityNot affected
Red Hat JBoss Data Grid 7spring-securityNot affected
Red Hat JBoss Enterprise Application Platform 6spring-securityOut of support scope
Red Hat JBoss Enterprise Application Platform 7spring-securityNot affected
Red Hat JBoss Enterprise Application Platform 8spring-securityNot affected
8 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-22234.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON