Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Getcomposer | Composer | 1.0.0 |
Related Weaknesses (CWE)
References
- https://flyingmana.de/blog_en/2016/02/14/composer_cache_injection_vulnerability_ExploitThird Party Advisory
- https://github.com/FriendsOfPHP/security-advisories/blob/e26be423c5bcfdb38478d2fThird Party Advisory
- https://github.com/composer/composerProduct
- https://gitlab.com/gitlab-org/advisories-community/-/blob/main/packagist/composeThird Party Advisory
- https://flyingmana.de/blog_en/2016/02/14/composer_cache_injection_vulnerability_ExploitThird Party Advisory
- https://github.com/FriendsOfPHP/security-advisories/blob/e26be423c5bcfdb38478d2fThird Party Advisory
- https://github.com/composer/composerProduct
- https://gitlab.com/gitlab-org/advisories-community/-/blob/main/packagist/composeThird Party Advisory
FAQ
What is CVE-2015-8371?
CVE-2015-8371 is a vulnerability with a CVSS score of 8.8 (HIGH). 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...
How severe is CVE-2015-8371?
CVE-2015-8371 has been rated HIGH with a CVSS base score of 8.8/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2015-8371?
Check the references section above for vendor advisories and patch information. Affected products include: Getcomposer Composer.