Locale-Independent Lowercase Conversion Vulnerability in libspring-java Package

libspring-java Updated 02 Oct 2025

Summary

16/05/2025
N/A
No i
Unrated
Not published

DEBIAN-CVE-2025-22233: CVE-2024-38820 ensured Locale-independent, lowercase conversion for both the configured disallowedFields patterns and for request parameter names. 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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libspring-java is a library that provides support for the Spring Framework, which is widely used for building Java applications. This library facilitates various functionalities such as dependency injection, aspect-oriented programming, and transaction management. The vulnerability in question affects the handling of request parameter names and disallowed fields, potentially allowing unauthorized access to sensitive data.

Vulnerability Detail

The vulnerability, identified as CVE-2024-38820, arises from the implementation of locale-independent, lowercase conversion for disallowedFields patterns and request parameter names. Despite these measures, there are still scenarios where attackers can bypass the disallowedFields checks, leading to potential exposure of sensitive data. This issue affects multiple versions of the Spring Framework, including 6.2.0 to 6.2.6, 6.1.0 to 6.1.19, 6.0.0 to 6.0.27, and 5.3.0 to 5.3.42, as well as older unsupported versions.

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 workaround, it is recommended to use a dedicated model object with properties only for data binding or to utilize constructor binding. This approach explicitly declares what to bind and disables setter binding through the declarativeBinding flag. Additionally, when setting binding, prefer using allowedFields (an explicit list) instead of disallowedFields.

Conclusion

The CVE-2024-38820 vulnerability in the libspring-java package poses a risk of unauthorized data access due to bypassed checks. Users are advised to upgrade to the patched versions to mitigate this risk effectively. Utilizing Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for libspring-java →

Share this vulnerability

FAQ

CVE-2024-38820 is a vulnerability in the Spring Framework that allows bypassing disallowedFields checks, potentially exposing sensitive data.

Affected versions include libspring-java in Debian:11, Debian:12, Debian:13, and Debian:14, specifically versions of the Spring Framework from 5.3.0 to 6.2.6.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

You should upgrade to the corresponding fixed version of the Spring Framework as outlined in the 'how to fix' section.

No further mitigation steps are necessary beyond upgrading to the fixed versions. However, consider using allowedFields for data binding.

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