CVE-2022-24346
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn JetBrains IntelliJ IDEA before 2021.3.1, local code execution via RLO (Right-to-Left Override) characters was possible.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIntelliJ IDEA before 2021.3.1 did not properly sanitize or handle RLO (Right-to-Left Override) Unicode control characters in file names. Attackers could craft malicious files with manipulated display names—using RLO to reverse the displayed file extension (e.g., making 'malware.txt.exe' appear as 'malware.txt')—to trick users into executing arbitrary code locally.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2021.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed IntelliJ IDEA versionOpen IntelliJ IDEA and go to Help > About (or on macOS, IntelliJ IDEA > About IntelliJ IDEA). Alternatively, check the installation directory name (e.g., 'IntelliJ IDEA 2021.3' or 'IntelliJ IDEA 2021.2.3') in Program Files/JetBrains/ on Windows or /Applications/ on macOS.Affected if The displayed version number is lower than 2021.3.1 (for example, 2021.3, 2021.2.4, 2021.1, etc.)
-
Verify IDE build number if version appears ambiguousIn Help > About, note the full build number (e.g., 'IC-213.5744.223'). Compare the build number to 213.5744.223, which corresponds to version 2021.3.1.Affected if The build number is less than 213.5744.223 (the build number for 2021.3.1).
-
Check for any recent IDE updatesIn the IDE, go to Help > Check for Updates to see if a newer version is available. Note that this requires network access.Affected if An update to version 2021.3.1 or later is available, indicating the current version is older and affected.
You are affected if your IntelliJ IDEA version is any build before 2021.3.1 (build 213.5744.223).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2021.3.1
Upgrade IntelliJ IDEA to version 2021.3.1 or later, which properly handles RLO characters in file names.
IntelliJ IDEA 2021.3.1 or later
- Check the current IntelliJ IDEA version by going to Help > About
- If the version is earlier than 2021.3.1, download IntelliJ IDEA 2021.3.1 or a later stable release from the official JetBrains website
- Install the updated version to remediate the RLO character local code execution vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24346 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24346 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data