CVE-2015-6420: Insecure Deserialization in Apache Commons Collection

Summary

15/06/2020
Yes i
High
Not published

CVE-2015-6420: Insecure Deserialization in Apache Commons Collection. Affects org.apache.commons:commons-collections4 versions < 4.1. Fixed in 4.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 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

Apache Commons Collections (ACC) is a Java library that provides additional collection classes and utilities. It is widely used in Java applications to enhance collection handling and manipulation. However, versions prior to 4.1 of the library are vulnerable to an insecure deserialization vulnerability.

Vulnerability Detail

The vulnerability, identified as CVE-2015-6420, allows remote attackers to execute arbitrary commands by exploiting the deserialization of serialized Java objects in applications that use the Apache Commons Collections library. By crafting a malicious serialized object, an attacker can execute arbitrary code on the target system, potentially leading to remote code execution and other security breaches.

How To Fix

Minimum fixed version

4.1

This is the first release that contains the fix.

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

Workaround

There is no known workaround for this vulnerability. It is essential to update the affected library to a secure version.

Conclusion

The insecure deserialization vulnerability in Apache Commons Collections can have severe consequences, including remote code execution. It is crucial for developers to update their applications to use a secure version of the library. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for org.apache.commons:commons-collections4 →

Share this vulnerability

FAQ

Apache Commons Collections is a Java library that provides additional collection classes and utilities to enhance collection handling and manipulation in Java applications.

Insecure deserialization is a vulnerability that occurs when an application deserializes untrusted data without proper validation. This can lead to the execution of arbitrary code and other security breaches.

This vulnerability can be exploited by crafting a malicious serialized Java object and sending it to an application that uses the vulnerable Apache Commons Collections library. When the object is deserialized, the attacker's code is executed.

Exploiting this vulnerability can lead to remote code execution, allowing attackers to execute arbitrary commands on the target system. This can result in unauthorized access, data breaches, and other security compromises.

Yes, the vulnerability has been fixed in version 4.1 and later of the Apache Commons Collections library. It is crucial to update to the latest secure version to mitigate the risk.

How To Fix

Minimum fixed version

4.1

This is the first release that contains the fix.

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