Code injection via predictable dist cache keys
Published Sep 21, 2023 · Updated Sep 25, 2024
Cache poisoning in Composer 1.0.0-alpha11 and earlier allows remote attackers to inject code into server-side builds via shared caches. Dist packages are cached under a key derived from the package name, distribution type, and repository-supplied reference, so a malicious repository can predict and prepopulate a key with a different archive. A build host must process the attacker's project and later build a victim project against the same cache, causing the victim build to consume attacker-controlled code.
Summary
What happened
Cache poisoning in Composer 1.0.0-alpha11 and earlier allows remote attackers to inject code into server-side builds via shared caches. Dist packages are cached under a key derived from the package name, distribution type, and repository-supplied reference, so a malicious repository can predict and prepopulate a key with a different archive. A build host must process the attacker's project and later build a victim project against the same cache, causing the victim build to consume attacker-controlled code.
The record
- CVE
- CVE-2015-8371
- Published
- Sep 21, 2023
- Updated
- Sep 25, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-345, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 21, 2023CVE publishedPublication date reported by the CVE source.
- Sep 25, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Composer cache injection proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo