Vulnerability in Getcomposer Composer
CVE-2015-8371
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.
EPSS: 0.007 (49.3th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
Affected products
- Getcomposer Composer — versions 1.0.0
- N/a — versions n/a
Weakness classification (CWE)
References
- cve@mitre.org (Exploit, Third Party Advisory)
- cve@mitre.org (Third Party Advisory)
- cve@mitre.org (Third Party Advisory)
- cve@mitre.org (Product)
Frequently asked questions
- What is CVE-2015-8371?
- CVE-2015-8371 is a high-severity vulnerability in Getcomposer Composer, classified under Insufficient Verification of Data Authenticity. CVSS score: 8.8/10. Published 2023-09-21.
- How severe is CVE-2015-8371?
- High severity. CVSS v3 base score is 8.8 out of 10.