Command execution hijack on Windows with Process class in symfony/process
symfony
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symfony/process Packagist |
|
|
| symfony/symfony Packagist |
symfony
| Product | Affected | Fixed in |
|---|---|---|
| symfony/process Packagist |
|
|
| symfony/symfony Packagist |
< 5.4.46≥ 6.0.0 · < 6.4.14≥ 7.0.0 · < 7.1.7
|
Symphony process is a module for the Symphony PHP framework which executes commands in sub-processes. On Windows, when an executable file named `cmd.exe` is located in the current working directory it will be called by the `Process` class when preparing command arguments, leading to possible hijacking. This issue has been addressed in release versions 5.4.46, 6.4.14, and 7.1.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.
From the CVE record · GitHub_M
On Windows, Symfony Process may call a file named `cmd.exe` in the current working directory while preparing command arguments. If an attacker can place that file there, they may hijack the command; the input does not specify authentication or user-interaction requirements.
Teams running Packagist `symfony/process` or `symfony/symfony` at versions below 5.4.46, from 6.0.0 to below 6.4.14, or from 7.0.0 to below 7.1.7 should check their Windows deployments.