Code execution via hijacked dependency namespace
Published Oct 11, 2022 · Updated May 19, 2025
Dependency confusion in d8s-lists 0.1.0 allows attackers to introduce arbitrary code through dependency resolution during installation. The release metadata declares democritus-dicts as a dependency even though that package name was no longer controlled by the d8s-lists maintainer, allowing a third party's package to satisfy it. Installing d8s-lists 0.1.0 is the required gate; public records do not identify when the dependency code executes or which privileges it inherits.
Summary
What happened
Dependency confusion in d8s-lists 0.1.0 allows attackers to introduce arbitrary code through dependency resolution during installation. The release metadata declares democritus-dicts as a dependency even though that package name was no longer controlled by the d8s-lists maintainer, allowing a third party's package to satisfy it. Installing d8s-lists 0.1.0 is the required gate; public records do not identify when the dependency code executes or which privileges it inherits.
The record
- CVE
- CVE-2022-42039
- Published
- Oct 11, 2022
- Updated
- May 19, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2022CVE publishedPublication date reported by the CVE source.
- May 19, 2025Record 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.
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
No public exploit references are available in this record.
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