cve.bz

CVE-2015-8371 getcomposer composer

8.8 highExploit referenceEPSS 0.7%Fix available

High (8.8) in getcomposer composer. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in composer/composer 1.0.0.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2024-09-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-345 Insufficient Verification of Data Authenticity
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2015-8371 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2015-8371?via=ask-ai-copy and https://cve.bz/cve/CVE-2015-8371?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2015-8371 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
getcomposer:composer1.0.0:alpha1
getcomposer:composer1.0.0:alpha10
getcomposer:composer1.0.0:alpha11
getcomposer:composer1.0.0:alpha2
getcomposer:composer1.0.0:alpha3
getcomposer:composer1.0.0:alpha4
getcomposer:composer1.0.0:alpha5
getcomposer:composer1.0.0:alpha6
getcomposer:composer1.0.0:alpha7
getcomposer:composer1.0.0:alpha8
getcomposer:composer1.0.0:alpha9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-725m-w832-q973Packagistcomposer/composer<1.0.01.0.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14composer1.0.0~alpha11-3DEBIAN-CVE-2015-8371

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stackJSON