dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-38819

HIGH · 7.5 CVSS v3.1 Published 2024-12-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Applications serving static resources through the functional web frameworks WebMvc.fn or WebFlux.fn are vulnerable to path traversal attacks. An attacker can craft malicious HTTP requests and obtain any file on the file system that is also accessible to the process in which the Spring application is running.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The vulnerability exists in Spring Framework's functional web frameworks (WebMvc.fn and WebFlux.fn) where static resource serving fails to properly validate path traversal sequences. Attackers can craft HTTP requests with '..' sequences to escape the intended static resource directory and access arbitrary files on the filesystem accessible to the application process.

MitigationUpgrade Spring Framework to version 6.1.12 or later / 6.0.23 or later / 5.3.39 or later, or implement strict path validation and whitelist-based static resource configuration to reject requests containing traversal sequences.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if functional web framework is in use
    Search the codebase for imports or usage of org.springframework.web.servlet.function.* or org.springframework.web.reactive.function.* These include RouterFunction, RouterFunctions, HandlerFunction, and similar functional routing constructs.
    Affected if The application uses WebMvc.fn or WebFlux.fn for request handling via RouterFunction or similar functional handlers.
  2. Verify static resource handling configuration
    Check for ResourceHandlerRegistry (WebMvc) or ResourceHandlerRegistration (WebFlux) configurations, or static resources served via RouterFunctions using the resource() method. Look for any .resources() calls in RouterFunction definitions.
    Affected if Static resources are configured to be served through Spring's resource handlers, particularly when chained to functional route definitions.
  3. Determine the Spring Framework version
    Inspect the Maven pom.xml or Gradle build file for spring-core, spring-webmvc, or spring-webflux dependency versions. Alternatively, at runtime check org.springframework.core.SpringVersion.getVersion() or the JAR manifest files in the classpath.
    Affected if The Spring Framework version is 6.1.x before 6.1.12, 6.0.x before 6.0.23, or 5.3.x before 5.3.39.
  4. Inspect request handling for path traversal exposure
    If functional routing and static resources are both in use, examine if any RouterFunction definitions serve static content without additional path validation. Check whether requests containing '..' sequences can reach static resource handlers.
    Affected if The functional routing setup serves static resources and allows '..' sequences to bypass intended directory boundaries.

A system is affected if it runs Spring Framework versions 6.1.x before 6.1.12, 6.0.x before 6.0.23, or 5.3.x before 5.3.39 AND uses WebMvc.fn or WebFlux.fn functional routing to serve static resources without additional path traversal validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Spring Framework to version 6.1.12 or later / 6.0.23 or later / 5.3.39 or later, or implement strict path validation and whitelist-based static resource configuration to reject requests containing traversal sequences.

Recommended fix High confidence

Spring Framework 5.3.39+ / 6.0.20+ / 6.1.12+ (choose the appropriate major version line)

  1. 1. Identify the Spring Framework version used in your application by checking your build configuration (pom.xml for Maven or build.gradle for Gradle)
  2. 2. If using Spring Framework 5.3.x, upgrade to version 5.3.39 or later
  3. 3. If using Spring Framework 6.0.x, upgrade to version 6.0.20 or later
  4. 4. If using Spring Framework 6.1.x, upgrade to version 6.1.12 or later
  5. 5. Rebuild and redeploy your application with the updated Spring Framework dependency
  6. 6. Verify static resource serving functionality works correctly after the upgrade
Caveat Likely minimal as this is a patch release, but review release notes for any behavioral changes in functional web framework static resource handling

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38819 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-38819 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data