Arbitrary code execution via malicious dependency
Published Jun 8, 2022 · Updated Aug 3, 2024
Code injection in the keep Python package 1.2 allows attackers to execute arbitrary code by installing its malicious request dependency. The affected distribution causes pip to install the malicious third-party request package, whose embedded backdoor executes code during dependency installation. Execution requires installation from an index or mirror that still serves the malicious dependency, and the backdoor runs with the installer process's privileges.
Summary
What happened
Code injection in the keep Python package 1.2 allows attackers to execute arbitrary code by installing its malicious request dependency. The affected distribution causes pip to install the malicious third-party request package, whose embedded backdoor executes code during dependency installation. Execution requires installation from an index or mirror that still serves the malicious dependency, and the backdoor runs with the installer process's privileges.
The record
- CVE
- CVE-2022-30877
- Published
- Jun 8, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 2022Exploitation reportedCompromised keep 1.2 package distribution
- 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.
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
- keep 1.2 malicious-dependency installation commandproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Compromised keep 1.2 package distributionreported exploitation
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