composer: Composer before 2016-02-10 allows cache poisoning from other projects built on the same host
CVE-2015-8371 is fixed in composer on 1 platform, first by DEBIAN-CVE-2015-8371, released September 21, 2023. It is not reported as exploited. Patch Radar priority: 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 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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| composer · Debian 12.15 (bookworm) | 1.0.0~alpha11-3 | DEBIAN-CVE-2015-8371 | Sep 21, 2023 |
| composer · Debian 13.5 (trixie) | 1.0.0~alpha11-3 | DEBIAN-CVE-2015-8371 | Sep 21, 2023 |
| composer · Debian 14 | 1.0.0~alpha11-3 | DEBIAN-CVE-2015-8371 | Sep 21, 2023 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.