Case Sensitivity Vulnerability in libspring-java Package

libspring-java Updated 02 Oct 2025

Summary

14/04/2022
N/A
No i
Unrated
Not published

DEBIAN-CVE-2022-22968: 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... Affects libspring-java versions 4.3.30-1 – 4.3.30-3. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

libspring-java is a core component of the Spring Framework, widely used for building Java applications. It provides comprehensive infrastructure support for developing Java applications, including data binding, validation, and more. This package is integral for developers who rely on Spring's capabilities to create robust applications. However, it is susceptible to a vulnerability that affects how fields are validated, particularly in terms of case sensitivity.

Vulnerability Detail

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. This means that if a field is listed as disallowed in a specific case, it will not be effectively protected unless it is also listed with both upper and lower case for the first character of the field. This vulnerability can lead to unauthorized access to sensitive data, as attackers may exploit the case sensitivity to bypass security measures.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, ensure that all disallowed fields are listed in both upper and lower case in your DataBinder configuration. This can be done by modifying your configuration file to include both variations of the field names.

Conclusion

The case sensitivity vulnerability in the libspring-java package poses a significant risk to applications relying on the Spring Framework. It is crucial for developers to update their packages to the latest versions and implement workarounds to mitigate potential risks. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for libspring-java →

Share this vulnerability

FAQ

The vulnerability is related to the case sensitivity of field names in the DataBinder's disallowedFields configuration, which can lead to inadequate protection against unauthorized access.

The affected versions include Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions.

You can use Vulert, which allows you to monitor and alert for open-source vulnerabilities in your software. You can check your application against this vulnerability using the Vulert playground at Vulert Scanner without any signup.

If exploited, this vulnerability can allow attackers to bypass security measures and gain unauthorized access to sensitive data within your application.

Yes, updating to a version of libspring-java that is later than 5.3.18 or 5.2.20 will resolve this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for libspring-java.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback