CVE-2015-8371: High severity composer vulnerability
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2015-8371?
CVE-2015-8371 has a high severity due to the potential for remote code execution via cache poisoning.
How do I fix CVE-2015-8371?
To fix CVE-2015-8371, update Composer to version 1.0.0 or later.
What are the affected versions of Composer for CVE-2015-8371?
Affected versions of Composer include all versions before 1.0.0, specifically up to 1.0.0-alpha11.
What type of vulnerability is CVE-2015-8371?
CVE-2015-8371 is a cache injection vulnerability that can be exploited to execute attacker-controlled code.
What impact does CVE-2015-8371 have on systems?
CVE-2015-8371 allows attackers to inject malicious code, which can compromise the integrity of server-side processes.