Skip to content

Composer allows cache poisoning from other projects built on the same host

High severity GitHub Reviewed Published Sep 21, 2023 to the GitHub Advisory Database • Updated Jan 24, 2024

Package

composer composer/composer (Composer)

Affected versions

<= 1.0.0-alpha11

Patched versions

1.0.0

Description

Composer before 2016-02-10 allows cache poisoning from other projects built on the same host. This results in attacker-controlled code entering a server-side build process. The issue occurs because of the way that dist packages are cached. The cache key is derived from the package name, the dist type, and certain other data from the package repository (which may simply be a commit hash, and thus can be found by an attacker). Versions through 1.0.0-alpha11 are affected, and 1.0.0 is unaffected.

References

Published by the National Vulnerability Database Sep 21, 2023
Published to the GitHub Advisory Database Sep 21, 2023
Reviewed Sep 21, 2023
Last updated Jan 24, 2024

Severity

High

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
Required
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.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS score

0.070%
(31st percentile)

Weaknesses

CVE ID

CVE-2015-8371

GHSA ID

GHSA-725m-w832-q973

Source code

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