Getcomposer Composer 1.0.0 Alpha 7

Submit a proposal Propose CVE/GCVE/GHSA reference

Approved changes feed: RSS · Atom

cpe:2.3:a:getcomposer:composer:1.0.0:alpha7:*:*:*:*:*:*

part: a version: 1.0.0 update: alpha7

VendorGetcomposer (e0bb4b7a-2fd0-5157-8692-1e509cd674da)
ProductComposer (2295e9c1-8c0c-5a78-ada8-82d842a89fe1)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:deb/debian/composer purl2cpe 2026-06-01 10:15:35.716183
pkg:deb/ubuntu/composer purl2cpe 2026-06-01 10:15:35.716184
pkg:docker/composer purl2cpe 2026-06-01 10:15:35.716186
pkg:github/composer/composer purl2cpe 2026-06-01 10:15:35.716187
pkg:rpm/fedora/composer purl2cpe 2026-06-01 10:15:35.716188
pkg:rpm/opensuse/composer purl2cpe 2026-06-01 10:15:35.716190
pkg:sourceforge/composer.mirror purl2cpe 2026-06-01 10:15:35.716191

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2015-8371 vulnerable 2026-06-08 05:07:03.795031 Details available
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.
Published: 2023-09-21T00:00:00.000Z
Updated: 2024-09-25T13:30:18.745Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.