
Cloud Vulnerability DB
A community-led vulnerabilities database
For projects that authenticate to a Composer repository using an inline HTTP header credential, a crafted composer.lock or vendor/composer/installed.json could cause that credential to be sent to a download mirror on an attacker-controlled host during composer install. This is an information disclosure issue limited to that repository credential. There is no code execution and no file modification.
You are affected if all of the following hold:
Authorization bearer token or an API key set in the repository's options (common with Private Packagist and Satis-style setups).composer.lock or vendor/composer/installed.json, for example through a pull request that edits the lock file, a committed lock in a shared project, or a poisoned CI cache.
When those hold, a crafted entry can add a preferred download mirror pointing at a host the attacker controls, and the repository credential is then sent to that host.
You are plainly not affected if your repositories do not use an inline header credential, or if you are on a release that does not re-attach repository headers at load time (any version other than 2.11.0, 2.11.1, and 2.2.31).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."