Skip to content
Fencer Intel
critical 9.1

CVE-2024-38821 in the critical feed json

Authorization Bypass of Static Resources in WebFlux Applications

published 2y ago modified 2mo ago also GHSA-c4q5-6c82-3qpw , EUVD-2024-3011

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

Summary

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

Patch / fix

  • maven org.springframework.security:spring-security-web 5.7.13, 5.8.15, 6.0.13, 6.1.11, 6.2.7, 6.3.4
  • Spring Spring 5.7.13, 5.8.15, 6.0.13, 6.1.11, 6.2.7, 6.3.4
  • spring webflux 5.7.13, 5.8.15, 6.0.13, 6.1.11, 6.2.7, 6.3.4

Is CVE-2024-38821 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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

Spring-WebFlux: Authorization Bypass of Static Resources in WebFlux Applications

  • Red Hat build of Apache Camel - HawtIO 4 org.springframework/spring-webflux org.springframework/spring-webflux Red Hat Fuse 7 org.springframework/spring-webflux org.springframework/spring-webflux Red Hat JBoss Enterprise Application Platform 7 org.springframework/spring-webflux org.springframework/spring-webflux Red Hat JBoss Enterprise Application Platform 8 org.springframework/spring-webflux org.springframework/spring-webflux Red Hat JBoss Enterprise Application Platform Expansion Pack org.springframework/spring-webflux org.springframework/spring-webflux
    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
yes
Technical impact
total
Assessed
2y ago

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/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-web
>=5.0.0, <5.7.13
>=5.8.0, <5.8.15
>=6.2.0, <6.2.7
>=6.0.0, <6.0.13
>=6.1.0, <6.1.11
>=6.3.0, <6.3.4
5.7.13
5.8.15
6.2.7
6.0.13
6.1.11
6.3.4

Affected products

  • Spring Spring
  • spring webflux

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling
  • CWE-285 Improper Authorization
Technology feeds

References

Sources

Fencer Intel 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.