Project trust bypass via unchecked build import
Published Mar 29, 2023 · Updated Feb 12, 2025
Improper authenticity verification in JetBrains IntelliJ IDEA before 2023.1 allows context-dependent attackers to bypass project trust. The Gradle and Maven import path begins project import without displaying the Trust Project confirmation; JetBrains has not disclosed the responsible code locus. A user must open an attacker-controlled local project, after which import permits dependency resolution and build-script execution that Safe Mode normally blocks.
Summary
What happened
Improper authenticity verification in JetBrains IntelliJ IDEA before 2023.1 allows context-dependent attackers to bypass project trust. The Gradle and Maven import path begins project import without displaying the Trust Project confirmation; JetBrains has not disclosed the responsible code locus. A user must open an attacker-controlled local project, after which import permits dependency resolution and build-script execution that Safe Mode normally blocks.
The record
- CVE
- CVE-2022-48431
- Published
- Mar 29, 2023
- Updated
- Feb 12, 2025
- Vendor
- JetBrains
- Product
- IntelliJ IDEA
- Classifications
- CWE-345, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 29, 2023CVE publishedPublication date reported by the CVE source.
- Feb 12, 2025Record 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=0 <2023.1
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