Getcomposer Composer 1.0.0 Alpha 4
Approved changes feed: RSS · Atom
cpe:2.3:a:getcomposer:composer:1.0.0:alpha4:*:*:*:*:*:*
part: a version: 1.0.0 update: alpha4
| Vendor | Getcomposer (e0bb4b7a-2fd0-5157-8692-1e509cd674da) |
|---|---|
| Product | Composer (2295e9c1-8c0c-5a78-ada8-82d842a89fe1) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:deb/debian/composer |
purl2cpe | 2026-06-01 10:15:35.716154 |
pkg:deb/ubuntu/composer |
purl2cpe | 2026-06-01 10:15:35.716156 |
pkg:docker/composer |
purl2cpe | 2026-06-01 10:15:35.716157 |
pkg:github/composer/composer |
purl2cpe | 2026-06-01 10:15:35.716159 |
pkg:rpm/fedora/composer |
purl2cpe | 2026-06-01 10:15:35.716160 |
pkg:rpm/opensuse/composer |
purl2cpe | 2026-06-01 10:15:35.716161 |
pkg:sourceforge/composer.mirror |
purl2cpe | 2026-06-01 10:15:35.716163 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2015-8371 |
vulnerable | 2026-06-08 05:07:03.793054 |
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.