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

CVE-2024-22234 · Severity: low · CVSS 3.1 · Published 2024-02-20

Broken Access Control in Spring Security With Direct Use of isFullyAuthenticated

Technologies: org.springframework.security:spring-security-core (Maven). Vendors: Maven.

Quick answers

Is CVE-2024-22234 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-22234 being exploited in the wild.
How severe is CVE-2024-22234?
Low severity, with a CVSS score of 3.1, published 20 February 2024.
Which products and versions are affected?
org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=6.1.0,fixed=6.1.7.
Is there a fix for CVE-2024-22234?
Yes. org.springframework.security:spring-security-core (Maven): upgrade to 6.1.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-22234?
Check whether you run org.springframework.security:spring-security-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.springframework.security:spring-security-core (Maven): upgrade to 6.1.7 or later
    # set org.springframework.security:spring-security-core to 6.1.7 in your pom.xml or build.gradle

Affected products

  • org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=6.1.0,fixed=6.1.7

Identifiers

  • CVE-2024-22234
  • GHSA-w3w6-26f2-p474

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.