Skip to content

Spring Framework DataBinder Case Sensitive Match Exception

Low severity GitHub Reviewed Published May 16, 2025 to the GitHub Advisory Database • Updated Jun 2, 2025

Package

maven org.springframework:spring-context (Maven)

Affected versions

>= 6.2.0, <= 6.2.6
>= 6.1.0, <= 6.1.19
>= 6.0.0, <= 6.0.23
<= 5.3.39

Patched versions

6.2.7
6.1.20

Description

CVE-2024-38820 ensured Locale-independent, lowercase conversion for both the configured disallowedFields patterns and for request parameter names. However, there are still cases where it is possible to bypass the disallowedFields checks.

Affected Spring Products and Versions

Spring Framework:

  • 6.2.0 - 6.2.6

  • 6.1.0 - 6.1.19

  • 6.0.0 - 6.0.27

  • 5.3.0 - 5.3.42

  • Older, unsupported versions are also affected

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.

Affected version(s) Fix Version  Availability
 6.2.x 6.2.7 OSS
6.1.x 6.1.20 OSS
6.0.x 6.0.28 Commercial https://enterprise.spring.io/
5.3.x 5.3.43 Commercial https://enterprise.spring.io/

No further mitigation steps are necessary.

Generally, we recommend using a dedicated model object with properties only for data binding, or using constructor binding since constructor arguments explicitly declare what to bind together with turning off setter binding through the declarativeBinding flag. See the Model Design section in the reference documentation.

For setting binding, prefer the use of allowedFields (an explicit list) over disallowedFields.

Credit

This issue was responsibly reported by the TERASOLUNA Framework Development Team from NTT DATA Group Corporation.

References

Published by the National Vulnerability Database May 16, 2025
Published to the GitHub Advisory Database May 16, 2025
Reviewed Jun 2, 2025
Last updated Jun 2, 2025

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(14th percentile)

Weaknesses

CVE ID

CVE-2025-22233

GHSA ID

GHSA-4wp7-92pw-q264

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.