CVE-2015-8371
Composer allows cache poisoning from other projects built on the same host
Reported by mitre · Published September 21, 2023
composer/composer is fixed in 1.0.0 (Packagist)
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| composer/composer | Packagist | 1.0.0 |
| composer | Ubuntu:16.04:LTS | 1.0.0~beta2-1 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
| composer | composer | 0 |
| n/a | n/a | * |
Timeline
- Feb 10, 2016 CVE Published
- Sep 22, 2023 EPSS Score (30 in total, the first dated here)
- Nov 21, 2024 CVE Updated
- Apr 3, 2026 Security Advisory
- Oct 11, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2015-8371
vulnetix vdb fixes CVE-2015-8371
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2015-8371/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart