Code deception via inadequate directionality warnings
Published Apr 28, 2022 · Updated Aug 3, 2024
Improper Unicode handling in JetBrains IntelliJ IDEA before 2022.1 allows local users to disguise source-code behavior with directionality controls. The editor notification mechanism does not adequately flag files containing Unicode directionality formatting characters, so displayed token order can differ from logical order. A user must open and trust attacker-influenced source text; the resulting visual deception can conceal an integrity-affecting code change.
Summary
What happened
Improper Unicode handling in JetBrains IntelliJ IDEA before 2022.1 allows local users to disguise source-code behavior with directionality controls. The editor notification mechanism does not adequately flag files containing Unicode directionality formatting characters, so displayed token order can differ from logical order. A user must open and trust attacker-influenced source text; the resulting visual deception can conceal an integrity-affecting code change.
The record
- CVE
- CVE-2022-29812
- Published
- Apr 28, 2022
- Updated
- Aug 3, 2024
- Vendor
- JetBrains
- Product
- IntelliJ IDEA
- Classifications
- CWE-176, T1036
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 28, 2022CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2022.1 <2022.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.
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