CVE-2024-35242: Composer has multiple command injections via malicious git/hg branch names

CVE-2024-35242 · Severity: low · CVSS 3.1 · Published 2024-06-10

Composer has multiple command injections via malicious git/hg branch names

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

Quick answers

Is CVE-2024-35242 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-35242 being exploited in the wild.
How severe is CVE-2024-35242?
Low severity, with a CVSS score of 3.1, published 10 June 2024.
Which products and versions are affected?
composer/composer (Packagist) ECOSYSTEM:introduced=2.0,fixed=2.2.24.
Is there a fix for CVE-2024-35242?
Yes. composer/composer (Packagist): upgrade to 2.2.24 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-35242?
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 2.2.24 or later
    composer require composer/composer:^2.2.24

Affected products

  • composer/composer (Packagist) ECOSYSTEM:introduced=2.0,fixed=2.2.24

Identifiers

  • CVE-2024-35242
  • GHSA-v9qv-c7wm-wgmf

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