Code execution via automatic Gradle build
Published May 11, 2021 · Updated Aug 3, 2024
Code execution in JetBrains IntelliJ IDEA before 2020.3.3 allows attackers to run arbitrary code when a developer clones a malicious Gradle project. The VCS project-loading path automatically starts the Gradle build task without first obtaining confirmation, causing attacker-controlled build logic to run. Exploitation requires a developer to clone or check out the repository; the code executes with the developer's privileges.
Summary
What happened
Code execution in JetBrains IntelliJ IDEA before 2020.3.3 allows attackers to run arbitrary code when a developer clones a malicious Gradle project. The VCS project-loading path automatically starts the Gradle build task without first obtaining confirmation, causing attacker-controlled build logic to run. Exploitation requires a developer to clone or check out the repository; the code executes with the developer's privileges.
The record
- CVE
- CVE-2021-29263
- Published
- May 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
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
- Malicious Gradle build proof of conceptproof 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