Symfony has incorrect argument escaping under MSYS2/Git Bash on Windows that can lead to destructive file operations
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.51, 6.4.33, 7.3.11, 7.4.5, 8.0.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to versions 5.4.51, 6.4.33, 7.3.11, 7.4.5, and 8.0.5, the Symfony Process component did not correctly treat some characters (notably `=`) as “special” when escaping arguments on Windows. When PHP is executed from an MSYS2-based environment (e.g. Git Bash) and Symfony Process spawns native Windows executables, MSYS2’s argument/path conversion can mis-handle unquoted arguments containing these characters. This can cause the spawned process to receive corrupted/truncated arguments compared to what Symfony intended. If an application (or tooling such as Composer scripts) uses Symfony Process to invoke file-management commands (e.g. `rmdir`, `del`, etc.) with a path argument containing `=`, the MSYS2 conversion layer may alter the argument at runtime. In affected setups this can result in operations being performed on an unintended path, up to and including deletion of the contents of a broader directory or drive. The issue is particularly relevant when untrusted input can influence process arguments (directly or indirectly, e.g. via repository paths, extracted archive paths, temporary directories, or user-controlled configuration). Versions 5.4.51, 6.4.33, 7.3.11, 7.4.5, and 8.0.5 contains a patch for the issue. Some workarounds are available. Avoid running PHP/one's own tooling from MSYS2-based shells on Windows; prefer cmd.exe or PowerShell for workflows that spawn native executables. Avoid passing paths containing `=` (and similar MSYS2-sensitive characters) to Symfony Process when operating under Git Bash/MSYS2. Where applicable, configure MSYS2 to disable or restrict argument conversion (e.g. via `MSYS2_ARG_CONV_EXCL`), understanding this may affect other tooling behavior.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- symfony symfony
fixed in 5.4.51; From 6.4.0 · fixed in 6.4.33; From 7.3.0 · fixed in 7.3.11; From 7.4.0 · fixed in 7.4.5; From 8.0.0 · fixed in 8.0.5
- symfony/processPackagist
fixed in 5.4.51
- symfony/processPackagist
From 6.4 · fixed in 6.4.33
- symfony/processPackagist
From 7.3 · fixed in 7.3.11
- symfony/processPackagist
From 7.4 · fixed in 7.4.5
- symfony/processPackagist
From 8.0 · fixed in 8.0.5
- symfony/symfonyPackagist
fixed in 5.4.51
- symfony/symfonyPackagist
From 6.4 · fixed in 6.4.33
- symfony/symfonyPackagist
From 7.3 · fixed in 7.3.11
- symfony/symfonyPackagist
From 7.4 · fixed in 7.4.5
- symfony/symfonyPackagist
From 8.0 · fixed in 8.0.5