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.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 8.8, indicating it can be exploited remotely over the network with relatively low complexity though user interaction is required and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 1 product from getcomposer organizations running these solutions should prioritize assessment and patching.
Reported in 2023, this vulnerability emerged during an era marked by increased sophistication in supply chain attacks, cloud infrastructure vulnerabilities, and software-as-a-service (SaaS) security challenges. Security practices during this period emphasized zero-trust architectures, container security, and API protection.
2023-09-21T06:15:11.633
2024-11-21T02:38:23.630
Modified
CVSSv3.1: 8.8 (HIGH)
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | getcomposer | composer | 1.0.0 | Yes |
| Application | getcomposer | composer | 1.0.0 | Yes |
| Application | getcomposer | composer | 1.0.0 | Yes |
| Application | getcomposer | composer | 1.0.0 | Yes |
| Application | getcomposer | composer | 1.0.0 | Yes |
| Application | getcomposer | composer | 1.0.0 | Yes |
| Application | getcomposer | composer | 1.0.0 | Yes |
| Application | getcomposer | composer | 1.0.0 | Yes |
| Application | getcomposer | composer | 1.0.0 | Yes |
| Application | getcomposer | composer | 1.0.0 | Yes |
| Application | getcomposer | composer | 1.0.0 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For getcomposer's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.