CVE-2015-8371

Name	CVE-2015-8371
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.
Source	CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)

Vulnerable and fixed packages

The table below lists information on source packages.

Source Package	Release	Version	Status
composer (PTS)	stretch (security)	1.2.2-1+deb9u1	fixed
	stretch (lts), stretch	1.2.2-1+deb9u3	fixed
	buster (security), buster, buster (lts)	1.8.4-1+deb10u4	fixed
	bullseye (security), bullseye	2.0.9-2+deb11u4	fixed
	bookworm (security), bookworm	2.5.5-1+deb12u2	fixed
	sid, trixie	2.8.3-1	fixed

The information below is based on the following data on fixed versions.

Package	Type	Release	Fixed Version	Urgency	Origin	Debian Bugs
composer	source	(unstable)	1.0.0~alpha11-3

http://flyingmana.de/blog_en/2016/02/14/composer_cache_injection_vulnerability_cve_2015_8371.html