CVE-2024-38821Public exploitNetwork attack vector

Unauthenticated static-resource access via unnormalized paths

Published Oct 28, 2024 · Updated Jan 24, 2025

Improper authorization in Spring Security 6.3.3 and earlier allows remote attackers to read protected static resources via crafted paths. WebFilterChainProxy matched raw, unnormalized request paths against security rules without a WebFlux firewall, so traversal segments could match a permitted static path before resource resolution reached a protected file. Exploitation requires WebFlux static-resource support and a non-permitAll rule protecting the requested resource; demonstrated impact is unauthorized file disclosure.

CVSS severity9.1
Critical
EPSS probability1.74%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authorization in Spring Security 6.3.3 and earlier allows remote attackers to read protected static resources via crafted paths. WebFilterChainProxy matched raw, unnormalized request paths against security rules without a WebFlux firewall, so traversal segments could match a permitted static path before resource resolution reached a protected file. Exploitation requires WebFlux static-resource support and a non-permitAll rule protecting the requested resource; demonstrated impact is unauthorized file disclosure.

The record

CVE
CVE-2024-38821
Published
Oct 28, 2024
Updated
Jan 24, 2025
Vendor
Spring
Product
Spring WebFlux
Classifications
CWE-770, CWE-285, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Oct 28, 2024CVE publishedPublication date reported by the CVE source.
  2. Jan 24, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.7.x <5.7.13
  2. Affected versionversion=5.8x <5.8.15
  3. Affected versionversion=6.0x <6.0.13
  4. Affected versionversion=6.1x <6.1.11
  5. Affected versionversion=6.2x <6.2.7
  6. Affected versionversion=6.3x <6.3.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Spring · Spring WebFluxversion=5.7.x <5.7.13; version=5.8x <5.8.15; version=6.0x <6.0.13; version=6.1x <6.1.11; version=6.2x <6.2.7; version=6.3x <6.3.4
Spring · Spring Frameworkversion=5.7.x <5.7.13; version=5.8.x <5.8.15; version=6.0.x <6.0.13; version=6.1.x <6.1.11; version=6.2.x <6.2.7; version=6.3.x <6.3.4

Published CVSS scores

9.1SpringCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
9.3GitHub Advisory DatabaseCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-770Allocation of Resources Without Limits or Throttling
CWE-285Improper Authorization
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo