8.8
CWE
345
Advisory Published
CVE Published
Updated

CVE-2015-8371

First published: Wed Feb 10 2016(Updated: )

Composer before 2016-02-10 allows cache poisoning from other projects built on the same host. This results in attacker-controlled code entering a server-side build process. The issue occurs because of the way that dist packages are cached. The cache key is derived from the package name, the dist type, and certain other data from the package repository (which may simply be a commit hash, and thus can be found by an attacker). Versions through 1.0.0-alpha11 are affected, and 1.0.0 is unaffected.

Credit: cve@mitre.org cve@mitre.org cve@mitre.org

Affected SoftwareAffected VersionHow to fix
composer/composer/composer<=1.0.0-alpha11
Getcomposer Composer=1.0.0-alpha1
Getcomposer Composer=1.0.0-alpha10
Getcomposer Composer=1.0.0-alpha11
Getcomposer Composer=1.0.0-alpha2
Getcomposer Composer=1.0.0-alpha3
Getcomposer Composer=1.0.0-alpha4
Getcomposer Composer=1.0.0-alpha5
Getcomposer Composer=1.0.0-alpha6
Getcomposer Composer=1.0.0-alpha7
Getcomposer Composer=1.0.0-alpha8
Getcomposer Composer=1.0.0-alpha9
composer/composer/composer<=1.0.0-alpha11
1.0.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203