CVE-2022-29813
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 custom Pandoc path 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 version 2022.1 allowed users to configure a custom path to the Pandoc executable (document conversion tool). This feature permitted local code execution because an attacker or malicious user with local access could specify a malicious executable as the Pandoc path, causing arbitrary code to be executed when IntelliJ invoked Pandoc.
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.
-
Check your IntelliJ IDEA versionOpen IntelliJ IDEA and go to Help > About (or on macOS IntelliJ IDEA > About IntelliJ IDEA). Note the version number displayed.Affected if The version shown is earlier than 2022.1 (for example, 2021.3, 2021.2, etc.)
-
Locate the Pandoc settingsGo to Settings (or Preferences on macOS) > Tools > Pandoc. Look for the Pandoc executable configuration section.Affected if The Pandoc settings panel is accessible and visible in your version of IntelliJ IDEA.
-
Identify if a custom Pandoc path is configuredIn the Pandoc settings panel, examine the field labeled 'Pandoc path' or similar. Check if it points to a custom executable location rather than using the default system Pandoc.Affected if A custom executable path is specified in the Pandoc path setting (for example, a path to a non-standard location or a custom-named executable).
You are affected if you are running any IntelliJ IDEA version before 2022.1 AND have configured a custom path to the Pandoc executable in the IDE settings.
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
Update IntelliJ IDEA to version 2022.1 or later. Until then, avoid configuring custom Pandoc paths and ensure only trusted users have local access to the machine.
IntelliJ IDEA 2022.1 or later
- Backup your project and IDE settings
- Uninstall the current IntelliJ IDEA version
- Download IntelliJ IDEA 2022.1 or later from the official JetBrains website (www.jetbrains.com)
- Install the new version following the installation wizard
- Restore your settings from the backup if needed
- Verify the installation by checking Help > About in IntelliJ IDEA
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29813 — 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-29813 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