CVE-2021-3129: Unauthenticated remote code execution in Ignition

CVE-2021-3129 · Severity: critical · CVSS 3.1 · Exploited in the wild · Published 2021-03-29

Ignition before 2.5.2, as used in Laravel and other products, contains a file upload vulnerability due to insecure usage of file_get_contents() and file_put_contents(). Unauthenticated remote attackers can exploit this on sites using debug mode to execute arbitrary code.

Technologies: Laravel Ignition, facade/ignition (Packagist). Vendors: Laravel, Packagist.

Quick answers

Is CVE-2021-3129 exploited in the wild?
Yes. CVE-2021-3129 is known to be exploited in the wild, first recorded on 18 September 2023. Treat it as urgent.
How severe is CVE-2021-3129?
Critical severity, with a CVSS score of 3.1, published 29 March 2021.
Which products and versions are affected?
facade/ignition (Packagist) ECOSYSTEM:introduced=2.5.0,fixed=2.5.2.
Is there a fix for CVE-2021-3129?
Yes. facade/ignition (Packagist): upgrade to 2.5.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2021-3129 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2021-3129?
Check whether you run Laravel Ignition or facade/ignition (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

  • facade/ignition (Packagist): upgrade to 2.5.2 or later
    composer require facade/ignition:^2.5.2

Affected products

  • Facade Ignition < 2.5.2
  • Laravel Laravel < 8.4.2

Identifiers

  • CVE-2021-3129
  • GHSA-4qwp-7c67-jmcc

Timeline

  • 2021-01-20: disclosed: Initial NVD analysis date
  • 2023-09-18: kev added: Added to CISA Known Exploited Vulnerabilities Catalog
  • 2023-09-18: advisory

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