Skip to content

Improper handling of case sensitivity in Spring Framework

High severity GitHub Reviewed Published Apr 15, 2022 to the GitHub Advisory Database • Updated May 15, 2024

Package

maven org.springframework:spring-context (Maven)

Affected versions

>= 5.3.0, < 5.3.19
< 5.2.21.RELEASE

Patched versions

5.3.19
5.2.21.RELEASE

Description

In Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions, the patterns for disallowedFields on a DataBinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field, including upper and lower case for the first character of all nested fields within the property path. Versions 5.3.19 and 5.2.21 contain a patch for this issue.

References

Published by the National Vulnerability Database Apr 14, 2022
Published to the GitHub Advisory Database Apr 15, 2022
Reviewed Apr 22, 2022
Last updated May 15, 2024

Severity

High

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
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
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:L/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.068%
(31st percentile)

Weaknesses

CVE ID

CVE-2022-22968

GHSA ID

GHSA-g5mm-vmx4-3rg7

Source code

Credits

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