
Cloud Vulnerability DB
A community-led vulnerabilities database
A malicious package archive could cause Composer to write a file outside the intended package directory during composer install, composer update, or composer require. Because the written file can be an application entry point or another file that later gets executed, this can lead to code execution. It is arbitrary file write, not a flaw triggered by normal Packagist-hosted packages, which do not carry the kind of archive entries required.
You are affected if all of the following hold:
unzip command available (standard on Linux and macOS) together with the PHP zip extension.
When those hold, a crafted archive can redirect one of its entries so the content lands outside the package directory, for example overwriting a front controller in the project root, which yields code execution on the next request or command.
You are plainly not affected if every package you install comes from a trusted source. Packagist.org-hosted archives generally do not contain the archive entries this relies on, so typical Packagist.org-only installs are not a realistic vector.
The single most realistic way to get hit: adding or updating a package served by an untrusted or attacker-controlled repository or mirror.Fixed in 2.11.2 and 2.2.32.
The only complete fix is upgrading.
Source: NVD
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."