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.
Weakness
The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.
Affected Software
| Name |
Vendor |
Start Version |
End Version |
| Spring_framework |
Vmware |
* |
5.2.0 (excluding) |
| Spring_framework |
Vmware |
5.2.0 (including) |
5.2.20 (including) |
| Spring_framework |
Vmware |
5.3.0 (including) |
5.3.18 (including) |
| Red Hat AMQ 7.10.0 |
RedHat |
springframework |
* |
| Red Hat Fuse 7.11 |
RedHat |
springframework |
* |
| Libspring-java |
Ubuntu |
bionic |
* |
| Libspring-java |
Ubuntu |
impish |
* |
| Libspring-java |
Ubuntu |
kinetic |
* |
| Libspring-java |
Ubuntu |
lunar |
* |
| Libspring-java |
Ubuntu |
mantic |
* |
| Libspring-java |
Ubuntu |
trusty |
* |
| Libspring-java |
Ubuntu |
trusty/esm |
* |
| Libspring-java |
Ubuntu |
xenial |
* |
Extended Description
Improperly handled case sensitive data can lead to several possible consequences, including:
Potential Mitigations
- Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
References