Skip to content
Fencer Vulns
high 7.4

CVE-2024-22234 json

CVE-2024-22234: Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated

published 2024-02-20 2 y ago modified 2026-06-17 4 mo ago also GHSA-w3w6-26f2-p474 , EUVD-2024-0745

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

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

Patch / fix

  • maven org.springframework.security:spring-security-core 6.1.7, 6.2.2
  • Spring Spring Security 6.1.7, 6.2.2
  • vmware spring_security 6.1.7, 6.2.2

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-22234 updated cvss 7.4

spring-security: Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated

  • Red Hat OpenShift Developer Tools and Services jenkins
    affected: workaround, no fix planned “Make sure the application is not vulnerable according to the description bullet points mentioned in this page.”
  • Red Hat build of Apache Camel for Spring Boot 4 spring-security spring-security
    affected: workaround, no fix available “Make sure the application is not vulnerable according to the description bullet points mentioned in this page.”
  • Red Hat Decision Manager 7 spring-security spring-security Red Hat Fuse 7 spring-security spring-security Red Hat JBoss Enterprise Application Platform 6 spring-security spring-security Red Hat JBoss Fuse 6 spring-security spring-security Red Hat JBoss Fuse Service Works 6 spring-security spring-security Red Hat Process Automation 7 spring-security spring-security
    affected: workaround, no fix planned “Make sure the application is not vulnerable according to the description bullet points mentioned in this page.”
  • Red Hat HawtIO 4.0.0 for Red Hat build of Apache Camel 4
    fixed: vendor fix “Make sure the application is not vulnerable according to the description bullet points mentioned in this page.” RHSA-2024:3550
  • Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2
    fixed: vendor fix “Make sure the application is not vulnerable according to the description bullet points mentioned in this page.” RHSA-2024:4884
  • Red Hat OpenShift Dev Spaces 3 devspaces/pluginregistry-rhel8 3.16-16
    fixed: vendor fix “Make sure the application is not vulnerable according to the description bullet points mentioned in this page.” RHSA-2024:6667
  • Red Hat A-MQ Clients 2 spring-security spring-security Red Hat build of Apache Camel for Spring Boot 3 spring-security spring-security Red Hat Build of Keycloak spring-security spring-security Red Hat build of Quarkus quarkus-spring-security Red Hat Data Grid 8 spring-security spring-security Red Hat Enterprise Linux 8 log4j, log4j-jcl, log4j-web, log4j-slf4j
    +11 more products
    Red Hat Enterprise Linux 9 log4j, log4j-jcl, log4j-slf4j Red Hat Integration Camel K 1 spring-security spring-security Red Hat JBoss Data Grid 7 spring-security spring-security Red Hat JBoss Enterprise Application Platform 7 spring-security spring-security Red Hat JBoss Enterprise Application Platform 8 spring-security spring-security Red Hat JBoss Enterprise Application Platform Expansion Pack spring-security spring-security Red Hat OpenShift Container Platform 3.11 jenkins Red Hat OpenShift Container Platform 4 jenkins Red Hat OpenShift Dev Spaces 3 devspaces/udi-rhel8 3.16-6, devspaces/idea-rhel8 3.16-3, devspaces/code-rhel8 3.16-20, devspaces/server-rhel8 3.16-14, devspaces/traefik-rhel8 3.16-2, devspaces/configbump-rhel8 3.16-4, +6 more Red Hat Single Sign-On 7 spring-security spring-security Red Hat streams for Apache Kafka spring-security spring-security
    not affected: vulnerable code not present

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
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.springframework.security:spring-security-core
>=6.1.0, <6.1.7
>=6.2.0, <6.2.2
6.1.7
6.2.2

Affected products

  • Spring Spring Security
  • vmware spring_security

Classification

Weakness
Technology feeds

References

Sources

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.