Remote Code Execution Vulnerability in Pivotal Spring Framework (CVE-2016-1000027)

libspring-java Updated 02 Oct 2025

Summary

02/01/2020
N/A
Yes i
Critical
9.8

CVE-2016-1000027: Pivotal Spring Framework through 5.3.16 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untrusted data. Affects libspring-java across 2 version ranges.

< 4.2.7-1 < 5a30a43b753a971ac8bf4005a8ccddeaff439d7e

Fixed in 4.2.7-1. 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

Pivotal Spring Framework is a popular open-source framework for building Java applications. It provides a comprehensive set of features and utilities to simplify the development process. However, versions up to 5.3.16 of the framework are vulnerable to a potential remote code execution (RCE) issue when used for Java deserialization of untrusted data. This vulnerability can lead to unauthorized execution of arbitrary code on the affected system. It is important to note that the framework is not intended to deserialize untrusted data, but some users may rely on deserialization of trusted data.

Vulnerability Detail

The vulnerability (CVE-2016-1000027) arises due to the insecure handling of Java deserialization of untrusted data in Pivotal Spring Framework. Depending on how the library is implemented within a product, this issue may or may not occur, and authentication may be required. An attacker can exploit this vulnerability by providing malicious serialized data, which can result in the execution of arbitrary code with the privileges of the application using the framework. The impact of this vulnerability can be severe, allowing an attacker to gain unauthorized access, manipulate data, or disrupt the normal functioning of the system.

How To Fix

Minimum fixed version

4.2.7-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade libspring-java

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. It is crucial to upgrade to the fixed version of the framework as soon as possible to eliminate the risk of remote code execution.

Conclusion

The remote code execution vulnerability (CVE-2016-1000027) in Pivotal Spring Framework can have severe consequences if exploited. It is crucial to upgrade to the fixed version of the framework (4.2.7-1 or later) to mitigate the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for libspring-java →

Share this vulnerability

FAQ

Pivotal Spring Framework is an open-source framework for building Java applications. It provides a wide range of features and utilities to simplify the development process.

This vulnerability can lead to remote code execution, allowing an attacker to execute arbitrary code on the affected system with the privileges of the application using the framework. This can result in unauthorized access, data manipulation, or disruption of system functionality.

Depending on how the library is implemented within a product, authentication may or may not be required to exploit this vulnerability.

There are no specific workarounds provided for this vulnerability. It is recommended to upgrade to the fixed version of the framework.

You can find more information about this vulnerability in the CVE-2016-1000027 JSON report available at the following source: https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2016-1000027.json

Related vulnerabilities

Recent vulnerabilities recorded for libspring-java.

How To Fix

Minimum fixed version

4.2.7-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade libspring-java

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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