Remote Code Execution Vulnerability in libspring-java

libspring-java Updated 02 Oct 2025

Summary

01/04/2022
N/A
No i
Critical
9.8

CVE-2022-22965: A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding. Affects libspring-java versions < cfa701b8726f06528e9d408b1b94f333f70da45f. 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 Java library used in Spring MVC and Spring WebFlux applications. It provides various functionalities for web development. The vulnerability affects applications running on JDK 9+ and deployed as a WAR on Tomcat. Spring Boot executable jars are not vulnerable. However, there may be other ways to exploit the vulnerability.

Vulnerability Detail

The vulnerability, identified as CVE-2022-22965, allows remote code execution (RCE) via data binding. An attacker can exploit this vulnerability to execute arbitrary code on the affected system. The exploit requires the application to run on Tomcat as a WAR deployment. The impact of this vulnerability can be severe, potentially leading to unauthorized access, data breaches, and system compromise.

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

If updating the libspring-java package is not immediately feasible, a possible workaround is to deploy the affected application as a Spring Boot executable jar instead of a WAR on Tomcat. This will prevent the specific exploit described in the vulnerability details. However, it is still essential to address the underlying vulnerability by updating the package.

Conclusion

The remote code execution vulnerability in libspring-java (CVE-2022-22965) poses a significant risk to applications running on JDK 9+ and deployed as a WAR on Tomcat. It is crucial to update the libspring-java package to a patched version or deploy the application as a Spring Boot executable jar to mitigate the risk. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for libspring-java →

Share this vulnerability

FAQ

libspring-java is a Java library used in Spring MVC and Spring WebFlux applications. It provides various functionalities for web development.

Applications running on JDK 9+ and deployed as a WAR on Tomcat are affected by this vulnerability. Spring Boot executable jars are not vulnerable.

The vulnerability allows remote code execution (RCE), which can lead to unauthorized access, data breaches, and system compromise.

To fix the vulnerability, update the libspring-java package to a version that includes the patch for CVE-2022-22965.

Yes, you can deploy the affected application as a Spring Boot executable jar instead of a WAR on Tomcat to prevent the specific exploit described in the vulnerability details. However, updating the libspring-java package is still necessary.

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