Code execution via untrusted dependency resolution
Published Nov 7, 2022 · Updated May 5, 2025
Dependency confusion in d8s-timer 0.1.0 allows attackers controlling a declared third-party package to execute code during installation. Its package metadata declares democritus-* dependencies whose names were no longer controlled by the maintainer, so package resolution can retrieve third-party code. Exploitation requires installation of the affected release and control of a declared dependency name; the public record inconsistently also names democritus-dates and d8s-htm.
Summary
What happened
Dependency confusion in d8s-timer 0.1.0 allows attackers controlling a declared third-party package to execute code during installation. Its package metadata declares democritus-* dependencies whose names were no longer controlled by the maintainer, so package resolution can retrieve third-party code. Exploitation requires installation of the affected release and control of a declared dependency name; the public record inconsistently also names democritus-dates and d8s-htm.
The record
- CVE
- CVE-2022-43306
- Published
- Nov 7, 2022
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, T1195.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 7, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 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.
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
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