Local code execution via DYLIB injection
Published Dec 8, 2022 · Updated Apr 22, 2025
DYLIB injection in JetBrains IntelliJ IDEA before 2022.3 allows local users to execute code in the IDE's context on macOS. JetBrains identifies the flaw only as DYLIB injection and has not published the affected executable, loading path, or unsafe library-resolution operation. A local low-privileged user must influence a dynamic library loaded by the IDE; successful injection runs attacker-controlled code with the IDE's access.
Summary
What happened
DYLIB injection in JetBrains IntelliJ IDEA before 2022.3 allows local users to execute code in the IDE's context on macOS. JetBrains identifies the flaw only as DYLIB injection and has not published the affected executable, loading path, or unsafe library-resolution operation. A local low-privileged user must influence a dynamic library loaded by the IDE; successful injection runs attacker-controlled code with the IDE's access.
The record
- CVE
- CVE-2022-46828
- Published
- Dec 8, 2022
- Updated
- Apr 22, 2025
- Vendor
- JetBrains
- Product
- IntelliJ IDEA
- Classifications
- CWE-691, T1574.006
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 8, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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 <2022.3
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