Arbitrary code execution via malicious request dependency
Published Jun 8, 2022 · Updated Aug 3, 2024
Malicious dependency installation in pyanxdns 0.2 allows attackers to execute arbitrary code when the package is installed. The setup.py install_requires list names the malicious request package instead of the legitimate requests dependency, causing pip to retrieve untrusted code. Execution requires a user or automated build to install the affected release from an index or mirror that still serves request.
Summary
What happened
Malicious dependency installation in pyanxdns 0.2 allows attackers to execute arbitrary code when the package is installed. The setup.py install_requires list names the malicious request package instead of the legitimate requests dependency, causing pip to retrieve untrusted code. Execution requires a user or automated build to install the affected release from an index or mirror that still serves request.
The record
- CVE
- CVE-2022-30882
- Published
- Jun 8, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 8, 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.
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
- Malicious dependency installation reproductionproof of concept · demonstrated
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