CVE-2022-29815
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 2022.1 local code execution via workspace settings 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 confidenceIn JetBrains IntelliJ IDEA versions prior to 2022.1, a vulnerability allowed local code execution through manipulation of workspace settings. An attacker with local access to the system could potentially execute arbitrary code by exploiting how the IDE processes workspace configuration files.
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< 2022.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/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.
-
Identify installed IntelliJ IDEA versionOpen IntelliJ IDEA and go to Help > About (on Windows/Linux) or IntelliJ IDEA > About (on macOS). The version number is displayed in the dialog that appears. Alternatively, check the installation directory for a version file or the application executable properties.Affected if The displayed version is any build number below 2022.1 (e.g., 2021.3.x, 2021.2.x, 2021.1.x, etc.)
-
Verify version from command lineIf the IDE is installed, locate the idea.sh (Linux/Mac) or idea.bat (Windows) executable in the installation bin directory and run it with a version flag, or check the product-info.json file typically found in the lib directory of the installation.Affected if The version output shows a build earlier than 2022.1
-
Confirm workspace configuration presenceLocate the workspace configuration files in the .idea directory within your project folders or the IDE configuration directory (typically ~/.IntelliJIdea/config on Linux/Mac or %USERPROFILE%\.IntelliJIdea\config on Windows). These XML-based workspace files store project settings.Affected if Workspace configuration files exist and the IDE version is below 2022.1, making exploitation possible through local access to these files
The environment is affected if IntelliJ IDEA is installed with any version prior to 2022.1, regardless of workspace configuration file presence.
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 · scoped2022.1
Upgrade JetBrains IntelliJ IDEA to version 2022.1 or later to remediate this vulnerability.
IntelliJ IDEA 2022.1
- Back up your current IntelliJ IDEA settings and projects
- Download IntelliJ IDEA 2022.1 from the official JetBrains website (www.jetbrains.com)
- Close any running instances of IntelliJ IDEA
- Install version 2022.1, using the installer for your operating system
- After installation, launch IntelliJ IDEA 2022.1
- Verify the IDE starts successfully and your projects load without errors
- Update any plugins if prompted to ensure compatibility with version 2022.1
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-29815 — 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-29815 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