CVE-2024-38821

CRITICAL

Published 2024-10-28T07:06:13.404Z

Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2024-38821. We'll provide specific mitigation strategies based on your environment and risk profile.

CVSS Score

V3.1

9.1

/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Base Score Metrics

Exploitability: N/A Impact: N/A

EPSS Score

v2025.03.14

0.106

probability

of exploitation in the wild

There is a 10.6% chance that this vulnerability will be exploited in the wild within the next 30 days.

Updated: 2025-06-25

Exploit Probability

Percentile: 0.929

Higher than 92.9% of all CVEs

Attack Vector Metrics

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Impact Metrics

Confidentiality

HIGH

Integrity

HIGH

Availability

NONE

Description

Spring WebFlux applications that have Spring Security authorization rules on static resources can be bypassed under certain circumstances.

For this to impact an application, all of the following must be true:

* It must be a WebFlux application
* It must be using Spring's static resources support
* It must have a non-permitAll authorization rule applied to the static resources support

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

Spring

Affected Versions:

5.7.x 5.8.x 6.0.x 6.1.x 6.2.x 6.3.x

spring

webflux

Affected Versions:

5.7.x 5.8x 6.0x 6.1x 6.2x 6.3x

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed CRITICAL

Spring Security vulnerable to Authorization Bypass of Static Resources in WebFlux Applications

GHSA-c4q5-6c82-3qpw

Advisory Details

Spring WebFlux applications that have Spring Security authorization rules on static resources can be bypassed under certain circumstances. For this to impact an application, all of the following must be true: * It must be a WebFlux application * It must be using Spring's static resources support * It must have a non-permitAll authorization rule applied to the static resources support