CVE-2025-22233: Spring Framework DataBinder Case Sensitive Match Exception
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.
Other sources
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 OSS6.1.x 6.1.20 OSS6.0.x 6.0.28 Commercial
— IBM
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/org.springframework:spring-contextto a version that resolves this vulnerability.Fixed in 6.1.20 - Upgrade
Upgrade
maven/org.springframework:spring-contextto a version that resolves this vulnerability.Fixed in 6.2.7 - Upgrade
Upgrade
Spring Frameworkto a version that resolves this vulnerability.Fixed in 5.3.43 - Upgrade
Upgrade
Spring Frameworkto a version that resolves this vulnerability.Fixed in 6.0.28 - Upgrade
Upgrade
Spring Frameworkto a version that resolves this vulnerability.Fixed in 6.1.20 - Upgrade
Upgrade
Spring Frameworkto a version that resolves this vulnerability.Fixed in 6.2.7 - Configuration
For setting binding, prefer the use of allowedFields (an explicit list) over disallowedFields. Mitigates bypass risk of disallowedFields checks mentioned in the document.
Spring Framework DataBinder (allowedFields/disallowedFields) disallowedFields = prefer allowedFields - Configuration
Use constructor binding and turn off setter binding through the declarativeBinding flag (as described: constructor arguments explicitly declare what to bind together with turning off setter binding via declarativeBinding).
Spring Framework DataBinder declarativeBinding flag = turn off setter binding - Configuration
Generally, use a dedicated model object with properties only for data binding (as recommended) to reduce the impact of the DataBinder case-sensitive match issue.
Spring Framework DataBinder use of dedicated model object for data binding = properties only for data binding
Event History
Frequently Asked Questions
What is the severity of CVE-2025-22233?
CVE-2025-22233 has a medium severity rating which indicates potential impacts on data integrity.
How do I fix CVE-2025-22233?
To fix CVE-2025-22233, it is recommended to upgrade to the latest version of Spring Framework that addresses this vulnerability.
What versions of Spring Framework are affected by CVE-2025-22233?
CVE-2025-22233 affects Spring Framework versions from 5.3.0 to 5.3.42, 6.0.0 to 6.0.27, 6.1.0 to 6.1.19, and 6.2.0 to 6.2.6.
What is the nature of the vulnerability in CVE-2025-22233?
CVE-2025-22233 allows bypassing of disallowedFields checks, potentially leading to unauthorized data access.
Is CVE-2025-22233 a critical vulnerability?
CVE-2025-22233 is not classified as critical but poses risks that should be addressed due to data integrity concerns.