Skip to content

Deserialization of Untrusted Data in Apache commons collections

Critical severity GitHub Reviewed Published May 13, 2022 to the GitHub Advisory Database • Updated Nov 2, 2023

Package

maven commons-collections:commons-collections (Maven)

Affected versions

< 3.2.2

Patched versions

3.2.2
maven net.sourceforge.collections:collections-generic (Maven)
= 4.01
None
maven org.apache.commons:commons-collections4 (Maven)
< 4.1
4.1
maven org.apache.servicemix.bundles:org.apache.servicemix.bundles.collections-generic (Maven)
>= 4.01, < 4.02
None
maven org.apache.servicemix.bundles:org.apache.servicemix.bundles.commons-collections (Maven)
>= 3.2.1, < 3.2.2
None

Description

It was found that the Apache commons-collections library permitted code execution when deserializing objects involving a specially constructed chain of classes. A remote attacker could use this flaw to execute arbitrary code with the permissions of the application using the commons-collections library.

References

Published by the National Vulnerability Database Nov 9, 2017
Published to the GitHub Advisory Database May 13, 2022
Reviewed Nov 3, 2022
Last updated Nov 2, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

2.226%
(90th percentile)

Weaknesses

CVE ID

CVE-2015-7501

GHSA ID

GHSA-fjq5-5j5f-mvxh

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.