dbcve.org
Intellij IdeaApplication · Jetbrains

CVE-2022-29814

HIGH · 7.7 CVSS v3.1 Published 2022-04-28
Fix available
A fix is available. Upgrade to 2022.1 or later.
See remediation →
77/100
Remediation priority · High

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 · unedited
In JetBrains IntelliJ IDEA before 2022.1 local code execution via HTML descriptions in custom JSON schemas 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 confidence

IntelliJ IDEA before version 2022.1 allowed local code execution through malicious HTML content embedded in custom JSON schema descriptions. When a user opens or previews a crafted JSON schema containing HTML/JavaScript in the description field, the embedded code executes in the context of the IDE, enabling local code execution.

MitigationUpgrade to IntelliJ IDEA 2022.1 or later. Avoid using untrusted or custom JSON schemas from unknown sources.

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
Intellij IdeaApplication
Affected:< 2022.1

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check IntelliJ IDEA version
    Open IntelliJ IDEA, go to Help > About (or on macOS IntelliJ IDEA > About IntelliJ IDEA). Note the version number displayed.
    Affected if The version shown is any version earlier than 2022.1 (for example, 2021.3, 2021.2, 2021.1, etc.)
  2. Identify custom JSON schema usage
    Go to Settings > Languages & Frameworks > JSON Schema. Review any configured custom JSON schemas, particularly those from unknown or untrusted sources.
    Affected if Custom JSON schemas are configured and those schemas contain HTML or JavaScript code in their description fields
  3. Check recent project files for custom schemas
    Search project directories for .json files with '$schema' entries pointing to non-standard or local schema files. Also check .idea/settings.json for JSON Schema mappings.
    Affected if Projects contain references to custom JSON schemas from untrusted or unknown sources that may include malicious descriptions
  4. Verify IDE context for schema preview
    Open any custom JSON schema file in the IDE and use the preview or syntax inspection feature (Schema Documentation or Ctrl+Q / F1) to view description fields.
    Affected if The description field in the JSON schema contains executable HTML or JavaScript content that could run in the IDE context

You are affected if running IntelliJ IDEA version earlier than 2022.1 AND using or previewing custom JSON schemas from untrusted sources that contain HTML/JavaScript in description fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2022.1 or later
Fixed in 2022.1
Interim mitigation

Upgrade to IntelliJ IDEA 2022.1 or later. Avoid using untrusted or custom JSON schemas from unknown sources.

Recommended fix High confidence

IntelliJ IDEA 2022.1 or later stable release

  1. Back up your IntelliJ IDEA settings, projects, and any custom configurations
  2. Download IntelliJ IDEA 2022.1 or a later stable version from the official JetBrains website (www.jetbrains.com/idea)
  3. Uninstall the current vulnerable version of IntelliJ IDEA, or install the new version alongside it
  4. Launch IntelliJ IDEA 2022.1 or later and verify the application starts successfully
  5. If using custom JSON schemas, verify they function correctly in the updated version
  6. Ensure your IDE updates to the latest patch releases within the 2022.1+ line for additional security fixes
Caveat Major IDE updates may include UI changes and require reconfiguration of some plugins; verify plugin compatibility with 2022.1+

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Intellij Idea Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-29814 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-29814 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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