← console
voxell vciy

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

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to the fixed version for your release line, or later: 6.1.7; 6.2.2 CVE record
  2. Later advisories still cover the fixes above and name higher ones: spring-security-core 6.2.3 (CVE-2024-22257), 6.2.8 (CVE-2024-38827) OSV advisories
  3. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  4. Check your version against the ranges this record publishes.

What it is stated by the CNA

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…

weakness
Not named by the CNA. NVD maps it to CWE-284.
affected
Spring Security
published ranges
vmware spring security >= 6.1.0 < 6.1.7; vmware spring security >= 6.2.0 < 6.2.2
fixed in
6.1.7; 6.2.2
fixed by package (from OSV advisories)
org.springframework.security:spring-security-core (Maven): 6.1.7; 6.2.2 GHSA-w3w6-26f2-p474
later fixes (from OSV advisories)
spring-security-core 6.1.7 is inside a range CVE-2024-22257 (GHSA-f3jh-qvm4-mg39) lists as affected. That advisory is fixed in 6.1.8.spring-security-core 6.1.7 is inside a range CVE-2024-38827 (GHSA-q3v6-hm2v-pw99) lists as affected. That advisory is fixed in 6.1.12.spring-security-core 6.2.2 is inside a range CVE-2024-22257 (GHSA-f3jh-qvm4-mg39) lists as affected. That advisory is fixed in 6.2.3.spring-security-core 6.2.2 is inside a range CVE-2024-38827 (GHSA-q3v6-hm2v-pw99) lists as affected. That advisory is fixed in 6.2.8.
severity
7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
assigned by
vmware
published
2024-02-20

check us spring.io security.netapp.com

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
20 Feb 20240.00043
17 Mar 20250.00644scoring model v2025.03.14
29 Mar 20250.06768
30 Mar 20250.00644
3 Apr 20250.0065
15 Apr 20250.0121
11 Jul 20250.01635
12 Oct 20250.01598
22 Oct 20250.01227
18 Nov 20250.00728
21 Nov 20250.01227
10 Mar 20260.01656
15 Jun 20260.00682scoring model v2026.06.15

13 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.01 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: 6.1.7; 6.2.2. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2024-22234', '2026-10-31T23:59:59.999999Z', now());