Project trust bypass via createProject misuse
Published Jun 18, 2024 · Updated Sep 11, 2025
Missing authorization in Bazel for IntelliJ before 2024.06.04.0.2 allows context-dependent attackers to bypass project trust during import. ProjectBuilder.createProject invokes ProjectManager.getInstance().createProject, a new-project path that omits the trust dialog required for imports. A user must import or auto-import an untrusted Bazel project; the project then opens without explicit source approval.
Summary
What happened
Missing authorization in Bazel for IntelliJ before 2024.06.04.0.2 allows context-dependent attackers to bypass project trust during import. ProjectBuilder.createProject invokes ProjectManager.getInstance().createProject, a new-project path that omits the trust dialog required for imports. A user must import or auto-import an untrusted Bazel project; the project then opens without explicit source approval.
The record
- CVE
- CVE-2024-5899
- Published
- Jun 18, 2024
- Updated
- Sep 11, 2025
- Vendor
- Bazel
- Product
- Bazel for IntelliJ (legacy)
- Classifications
- CWE-862, T1204
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 18, 2024CVE publishedPublication date reported by the CVE source.
- Sep 11, 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 <2024.06.04.0.2
What conditions does exploitation require?
What is affected?
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.
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