Code execution via malicious request dependency
Published Jul 22, 2022 · Updated Aug 3, 2024
A code execution backdoor in bin-collect 0.1 and earlier allows attackers to execute arbitrary code when the Python package is installed. Package metadata names the malicious request dependency instead of the legitimate requests library, so pip can retrieve attacker-supplied code from a retaining mirror. Exploitation requires installation through a package index that still serves request, and code runs with the installer's privileges.
Summary
What happened
A code execution backdoor in bin-collect 0.1 and earlier allows attackers to execute arbitrary code when the Python package is installed. Package metadata names the malicious request dependency instead of the legitimate requests library, so pip can retrieve attacker-supplied code from a retaining mirror. Exploitation requires installation through a package index that still serves request, and code runs with the installer's privileges.
The record
- CVE
- CVE-2022-34500
- Published
- Jul 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 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