CVE-2022-29819
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 links in Quick Documentation 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 confidenceThis vulnerability in JetBrains IntelliJ IDEA versions before 2022.1 allows local code execution via malicious links embedded in the Quick Documentation feature. An attacker could potentially execute arbitrary code on the developer's local machine by crafting malicious documentation links.
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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/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.
-
Verify IntelliJ IDEA is installedCheck for IntelliJ IDEA installation in typical locations: Windows: C:\Program Files\JetBrains\IntelliJ IDEA, macOS: /Applications/IntelliJ IDEA, Linux: ~/jetbrains or /opt/idea. Or run 'idea' command if available.Affected if IntelliJ IDEA is not found on the system, the check does not apply.
-
Determine installed IntelliJ IDEA versionOpen IntelliJ IDEA and navigate to Help > About (or Help > About IntelliJ IDEA on macOS) to display the version number. Alternatively, check the installation directory for a version file or release notes.Affected if The installed version is a release before 2022.1 (e.g., 2021.x, 2020.x, etc.).
-
Confirm Quick Documentation feature existsIn IntelliJ IDEA, verify the Quick Documentation feature is available by hovering over a code element while holding Ctrl (Windows/Linux) or Cmd (macOS), or pressing Ctrl+Q / Cmd+Q. This feature is part of the standard IDE functionality.Affected if The Quick Documentation feature is present and can be invoked on the system.
-
Compare version against affected rangeIf a version number is identified, compare it to the affected range: any version lower than 2022.1 is vulnerable. Examples: 2021.3.3, 2021.2, 2021.1, 2020.3 are all in the affected range.Affected if The installed version is a 2021.x or earlier release (version < 2022.1).
The environment is affected if IntelliJ IDEA is installed with a version lower than 2022.1 and the Quick Documentation feature is accessible.
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 IntelliJ IDEA to version 2022.1 or later to remediate this vulnerability. Verify that the Quick Documentation feature functions correctly after the upgrade.
IntelliJ IDEA 2022.1
- Download IntelliJ IDEA 2022.1 or later from the official JetBrains website (www.jetbrains.com)
- Install the new version, ensuring you back up your settings if needed
- Verify the installed version shows 2022.1 or higher in Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29819 — 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-29819 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