Code execution via automatic virtual environment activation
Published May 11, 2021 · Updated Aug 3, 2024
Code execution in JetBrains PyCharm before 2020.3.4 allows remote attackers to run commands when a user opens a crafted VCS project. PyCharm automatically activates a virtual environment bundled in a newly opened project, executing attacker-controlled commands from its activation script without first requesting confirmation. Exploitation requires a user to fetch and open the untrusted repository, after which the commands run with that user's privileges.
Summary
What happened
Code execution in JetBrains PyCharm before 2020.3.4 allows remote attackers to run commands when a user opens a crafted VCS project. PyCharm automatically activates a virtual environment bundled in a newly opened project, executing attacker-controlled commands from its activation script without first requesting confirmation. Exploitation requires a user to fetch and open the untrusted repository, after which the commands run with that user's privileges.
The record
- CVE
- CVE-2021-30005
- Published
- May 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-345, T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- May 11, 2021CVE 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
- CVE-2021-30005-POCproof 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