IDE-user compromise via unsandboxed bundled Chromium
Published Mar 29, 2023 · Updated Feb 12, 2025
Sandbox isolation failure in JetBrains IntelliJ IDEA before 2023.1 allows local users to compromise the IDE process via embedded web content. The bundled Chromium runtime starts without its sandbox, so renderer code handling untrusted content lacks Chromium's intended operating-system containment. Exploitation requires user interaction and a separate Chromium compromise, after which code can access data and resources available to the IDE user.
Summary
What happened
Sandbox isolation failure in JetBrains IntelliJ IDEA before 2023.1 allows local users to compromise the IDE process via embedded web content. The bundled Chromium runtime starts without its sandbox, so renderer code handling untrusted content lacks Chromium's intended operating-system containment. Exploitation requires user interaction and a separate Chromium compromise, after which code can access data and resources available to the IDE user.
The record
- CVE
- CVE-2022-48432
- Published
- Mar 29, 2023
- Updated
- Feb 12, 2025
- Vendor
- JetBrains
- Product
- IntelliJ IDEA
- Classifications
- CWE-1188, T1203
- 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?
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.
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