Arbitrary code execution via unclaimed dependency
Published Sep 19, 2022 · Updated Aug 3, 2024
Dependency confusion in d8s-dates 0.1.0 allows attackers to execute arbitrary code through a malicious PyPI dependency. Its requirements file passes the unversioned democritus-hypothesis name to package resolution even though the maintainer no longer controlled that name, permitting a third-party distribution to satisfy it. Exposure requires installing d8s-dates 0.1.0 from PyPI; the public records do not disclose which package hook executes the dependency code.
Summary
What happened
Dependency confusion in d8s-dates 0.1.0 allows attackers to execute arbitrary code through a malicious PyPI dependency. Its requirements file passes the unversioned democritus-hypothesis name to package resolution even though the maintainer no longer controlled that name, permitting a third-party distribution to satisfy it. Exposure requires installing d8s-dates 0.1.0 from PyPI; the public records do not disclose which package hook executes the dependency code.
The record
- CVE
- CVE-2022-40808
- Published
- Sep 19, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 19, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
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