Skip to content

Composer 2.11.2 patches a command execution bug in composer.lock

A CVSS 8.8 flaw let a crafted lock file run arbitrary commands during install, bypassing --no-scripts and --no-plugins. Two more fixes patch a zip file-write bug and a credential leak to rogue mirrors.

Source: Composer

Composer released 2.11.2, alongside 2.2.32 for its older LTS branch, on 10 November, fixing three security bugs. The worst, GHSA-jhfp-4ppm-crmm with a CVSS score of 8.8, let a crafted composer.lock or vendor/composer/installed.json set the prevent_url_access_callable transport option, which could trigger an arbitrary command during install or update. Running composer install with --no-scripts and --no-plugins does not stop it, since the flaw sits in Composer’s own download handling rather than in project scripts. It affects Composer 2.10.0 through 2.11.1.

The same release fixes a second CVSS 8.8 bug where a malicious zip archive could write files outside the package directory via symlinked entries, and a CVSS 6.5 flaw where a tampered lock file could redirect a download to an attacker’s mirror and leak repository credentials to it.

composer self-update

Why it matters: the command execution bug is exploitable by anything that controls your lock file, a compromised dependency, a pull request your CI builds unreviewed, or a tampered package on Packagist. If your CI runs composer install against lock files it didn’t generate itself, this is the one to patch first.

Share

Related reading

More from The Wire

All briefs