Check the status of CVEs. Learn More.
Compliance + Protection: Strengthen your cybersecurity defenses with TuxCare’s Security Hardening – or gain painless FIPS 140-3 compliance with Extended Security Updates.
This CVE has been resolved by the TuxCare team and
a patch has been delivered to ELS for Spring users.
Spring Security is a powerful authentication and access control framework for Java applications, particularly those built using the Spring Framework. It provides a comprehensive security solution, addressing various concerns such as authentication, authorization, and protection against common security vulnerabilities.
“Allocation of Resources without Limits” or “Throttling” takes place when the product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor.
CVE-2024-38821 is a critical authorization bypass vulnerability identified in Spring WebFlux applications that utilize Spring Security for access control on static resources. This flaw allows unauthorized users to access restricted static resources under specific conditions.
This issue affects multiple versions of: org.springframework.security:spring-security-web package.
Vulnerability Dossier | |
---|---|
CVE ID | CVE-2024-38821 |
Severity | Critical: 9.1 |
CWE-ID and name | CWE-770: Allocation of Resources Without Limits or Throttling |
Affected project | Spring Security |
Affected packages | spring-security-web |
Affected versions | 5.6.2 and older, <5.7.0;5.7.12>, <5.8.0;5.8.14>, <6.0.0;6.0.12>, <6.1.0;6.1.10>, <6.2.0;6.2.6>, <6.3.0;6.3.3> |
NVD publish date | 28th of October 2024 (Spring.io: 22nd of October 2024) |
Open source fix date | 21st of October 2024 |
Open Source fixed versions | 5.8.15 |
Spring WebFlux applications that utilize Spring’s static resources support and have non-permitAll authorization rules applied to them may, under specific conditions, be vulnerable to unauthorized access of static resources. The vulnerability can be exploited if the application meets all the following criteria:
Why Is This a Problem?
When all the above conditions are met, the vulnerability may permit unauthorized access to static resources, potentially exposing sensitive information or functionality.
Set Up a Vulnerable Application:
Attempt Unauthorized Access:
Proof of Concept (PoC): Security researcher Mouad Kondah has provided a detailed explanation and a PoC exploit demonstrating how this vulnerability can be exploited by manipulating URL paths to bypass security filters here.
Mitigation
Spring Security 5.8.x is no longer supported by the open source community, as its End of Life date was on 2023-12-31. This means that the version from that date does not receive any updates to address this issue.
Users of the affected components should apply one of the following mitigations:
If you need a fix for this vulnerability or for any other Spring Security version, please contact us, we are here to help you!