CVE-2022-24345
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.2.4, local code execution (without permission from a user) upon opening a project 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 · moderate confidenceIntelliJ IDEA versions before 2021.2.4 contained a vulnerability allowing local code execution without user permission when opening a malicious project. An attacker could craft a project file that triggers arbitrary code execution upon project opening in the IDE.
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.2.4CVSS 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 your installed IntelliJ IDEA versionOpen IntelliJ IDEA and navigate to Help > About (or on macOS, IntelliJ IDEA > About). The version number is displayed in the dialog that appears. Alternatively, check the installation directory or your system's installed programs list for the version information.Affected if The displayed version is earlier than 2021.2.4 (for example, 2021.2, 2021.1, 2020.3, etc.)
-
Verify the full version number including patchIn the About dialog, note the full version string which includes the patch number (for example, 2021.2.3). Compare this against 2021.2.4.Affected if The version is 2021.2.3 or earlier, meaning the patch level is less than 4
-
Assess whether you open projects from untrusted sourcesConsider your typical workflow: do you occasionally open project files, repositories, or ZIP archives from unfamiliar or untrusted sources, or are all your projects from known trusted origins?Affected if You open projects from untrusted or unfamiliar sources and your version is before 2021.2.4
You are affected if your IntelliJ IDEA version is any release before 2021.2.4 and you open projects from untrusted sources, as the vulnerability triggers simply by opening a malicious project file.
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.2.4
Update IntelliJ IDEA to version 2021.2.4 or later. Avoid opening untrusted or unfamiliar projects from untrusted sources.
2021.2.4 (build 212.5284.40)
- Open IntelliJ IDEA and navigate to Help > Check for Updates
- If an update is available, download and install version 2021.2.4 or later
- Alternatively, download the fixed version directly from jetbrains.com/idea/download/
- Restart IntelliJ IDEA after the update completes
- Verify the version by going to Help > About and confirm the build number is 212.5284.40 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24345 — 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-24345 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