Local code execution via Vagrant executable
Published Jul 28, 2022 · Updated Aug 3, 2024
Code injection in JetBrains IntelliJ IDEA before 2022.2 allows local users to execute code via a Vagrant executable. JetBrains identifies the Vagrant executable as the vector but has not disclosed the affected function or the operation performed on untrusted input. Exploitation requires low-privileged local access and user interaction; successful execution runs attacker-controlled code in the IDE's security context.
Summary
What happened
Code injection in JetBrains IntelliJ IDEA before 2022.2 allows local users to execute code via a Vagrant executable. JetBrains identifies the Vagrant executable as the vector but has not disclosed the affected function or the operation performed on untrusted input. Exploitation requires low-privileged local access and user interaction; successful execution runs attacker-controlled code in the IDE's security context.
The record
- CVE
- CVE-2022-37009
- Published
- Jul 28, 2022
- Updated
- Aug 3, 2024
- Vendor
- JetBrains
- Product
- IntelliJ IDEA
- Classifications
- CWE-94
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 28, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2022.2 <2022.2
What conditions does exploitation require?
What is affected?
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