CVE-2015-8371: Composer allows cache poisoning from other projects built on the same host

CVE-2015-8371 · Severity: low · CVSS 3.1 · Published 2023-09-21

Composer allows cache poisoning from other projects built on the same host

Technologies: composer/composer (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2015-8371 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2015-8371 being exploited in the wild.
How severe is CVE-2015-8371?
Low severity, with a CVSS score of 3.1, published 21 September 2023.
Which products and versions are affected?
composer/composer (Packagist) ECOSYSTEM:introduced=0,fixed=1.0.0.
Is there a fix for CVE-2015-8371?
Yes. composer/composer (Packagist): upgrade to 1.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2015-8371?
Check whether you run composer/composer (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • composer/composer (Packagist): upgrade to 1.0.0 or later
    composer require composer/composer:^1.0.0

Affected products

  • composer/composer (Packagist) ECOSYSTEM:introduced=0,fixed=1.0.0

Identifiers

  • CVE-2015-8371
  • GHSA-725m-w832-q973

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.