Code execution via dependency-confusion package install
Published Oct 11, 2022 · Updated May 20, 2025
Dependency confusion in d8s-archives 0.1.0 allows attackers to execute code by supplying its democritus-file-system dependency. The release declares a PyPI package name outside the maintainer's control, causing pip to resolve and install third-party code. Exploitation requires installation of the affected release while an attacker-controlled dependency is available, and code runs with the installer's privileges.
Summary
What happened
Dependency confusion in d8s-archives 0.1.0 allows attackers to execute code by supplying its democritus-file-system dependency. The release declares a PyPI package name outside the maintainer's control, causing pip to resolve and install third-party code. Exploitation requires installation of the affected release while an attacker-controlled dependency is available, and code runs with the installer's privileges.
The record
- CVE
- CVE-2022-41383
- Published
- Oct 11, 2022
- Updated
- May 20, 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 20, 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