CVE-2024-24821: Composer code execution and possible privilege escalation via compromised InstalledVersions.php or installed.php

CVE-2024-24821 · Severity: low · CVSS 3.1 · Published 2024-02-08

Composer code execution and possible privilege escalation via compromised InstalledVersions.php or installed.php

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

Quick answers

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

Affected products

  • composer/composer (Packagist) ECOSYSTEM:introduced=2.0.0-alpha1,fixed=2.2.23

Identifiers

  • CVE-2024-24821
  • GHSA-7c6p-848j-wh5h

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