CVE-2015-8371 json
Composer allows cache poisoning from other projects built on the same host
published 3y ago modified 4mo ago also GHSA-725m-w832-q973 , EUVD-2023-2452
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- packagist composer/composer 1.0.0
- composer Debian 14, Debian 13, Debian 12 1.0.0~alpha11-3
debian advisories DEBIAN-CVE-2015-8371
Is CVE-2015-8371 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- flyingmana.de https://flyingmana.de/blog_en/2016/02/14/composer_cache_injection_vulnerability_cve_2015_8371.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | composer/composer | <1.0.0 |
1.0.0 |
Classification
- Weakness
-
- CWE-345 Insufficient Verification of Data Authenticity
References
-
flyingmana.de
/blog_en/2016/02/14/composer_cache_injection_vulnerability_cve_2015_8371.html
web, exploit, third-party-advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/e26be423c5bcfdb38478d2f92d1f928c15afb561/composer/composer/CVE-2015-837
web, third-party-advisory
-
gitlab.com
/gitlab-org/advisories-community/-/blob/main/packagist/composer/composer/CVE-2015-8371.yml
web, third-party-advisory
-
github.com
/composer/composer
package, product
-
nvd.nist.gov
/vuln/detail/CVE-2015-8371
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/composer/composer/CVE-2015-8371.yaml
web
-
flyingmana.de
/blog_en/2016/02/14/composer_cache_injection_vulnerability_cve_2015_8371.html
web
Sources
- CVE List CVE-2015-8371
- GitHub Advisory GHSA-725m-w832-q973
- NVD CVE-2015-8371
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.