Advisory

GHSA-725m-w832-q973

Also known as: CVE-2015-8371

Summary

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

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2023-09-21 06:30 UTC
Modified
2024-02-16 08:06 UTC

Affected packages and fixes

composer/composer

Packagist · All systems

Affected

  • introduced 0, fixed 1.0.0 (ecosystem)

Fixed versions

1.0.0

Fix

The export has no generic command for this ecosystem.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences