CVE-2024-38820Network attack vector

Protected-field modification via locale-dependent case folding

Published Oct 18, 2024 · Updated Nov 29, 2024

Improper case handling in Spring Framework allows remote authenticated users to modify fields blocked by DataBinder patterns. The DataBinder.setDisallowedFields and isAllowed paths canonicalize patterns and candidate names with the JVM default locale, so locale-specific lowercase results can prevent a configured pattern from matching an attacker-controlled property name. Exposure requires an application to bind attacker-controlled property names through DataBinder with disallowedFields under a locale that folds relevant characters differently; successful requests write fields the application intended to exclude.

CVSS severity2.7
Low
EPSS probability0.62%
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 case handling in Spring Framework allows remote authenticated users to modify fields blocked by DataBinder patterns. The DataBinder.setDisallowedFields and isAllowed paths canonicalize patterns and candidate names with the JVM default locale, so locale-specific lowercase results can prevent a configured pattern from matching an attacker-controlled property name. Exposure requires an application to bind attacker-controlled property names through DataBinder with disallowedFields under a locale that folds relevant characters differently; successful requests write fields the application intended to exclude.

The record

CVE
CVE-2024-38820
Published
Oct 18, 2024
Updated
Nov 29, 2024
Vendor
Spring
Product
Spring Framework
Classifications
CWE-178, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 18, 2024CVE publishedPublication date reported by the CVE source.
  2. Nov 29, 2024Record 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.3.x <5.3.41
  2. Affected versionversion=6.0.x <6.0.25
  3. Affected versionversion=6.1.x <6.1.14

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Spring · Spring Frameworkversion=5.3.x <5.3.41; version=6.0.x <6.0.25; version=6.1.x <6.1.14

Published CVSS scores

5.3GitHub Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
2.7SpringCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A: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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-178Improper Handling of Case Sensitivity
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

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