Intellij IdeaApplication · Jetbrains

CVE-2022-47896

HIGH · 7.8 CVSS v3.1 Published 2022-12-22

Fix available

A fix is available. Upgrade to 2022.3.1 or later.

See remediation →

80/100

Remediation priority · High

Zero-click

Official description

NVD · unedited

In JetBrains IntelliJ IDEA before 2022.3.1 code Templates were vulnerable to SSTI attacks.

Technical summary

dbcve analysis · high confidence

JetBrains IntelliJ IDEA versions prior to 2022.3.1 contained a Server-Side Template Injection (SSTI) vulnerability in the code Templates feature. This allowed malicious template directives within code templates to execute arbitrary code on the developer's machine when the template was processed.

MitigationUpgrade IntelliJ IDEA to version 2022.3.1 or later to remediate the SSTI vulnerability in code Templates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Intellij IdeaApplication

Affected:< 2022.3.1

CVSS breakdown

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?

dbcve checks

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

Verify IntelliJ IDEA is installed

Check for IntelliJ IDEA installation directories (typically at /Applications on macOS, C:\Program Files\JetBrains on Windows, or ~/JetBrains on Linux). On command line, run: which idea (Linux/macOS) or where idea (Windows)

Affected if IntelliJ IDEA is not found on the system, the user is not affected by this specific product vulnerability
Determine installed IntelliJ IDEA version

Open IntelliJ IDEA and go to Help > About (or use the command: ls /Applications/IntelliJ\ IDEA*.app/Contents/Info.plist 2>/dev/null | xargs grep -i "CFBundleShortVersionString" on macOS; on Windows check the installation folder for version.txt or launch the IDE and check Help > About)

Affected if The displayed version number is missing or cannot be determined
Compare version against affected range

Check if the installed version is less than 2022.3.1. Version format is typically YYYY.X.Z (e.g., 2022.3.0, 2022.2.3, 2021.3.5)

Affected if Installed version is 2022.3.0 or earlier (e.g., 2022.2.x, 2021.3.x, etc.)
Inspect code templates configuration

In IntelliJ IDEA, go to Settings/Preferences > Editor > File and Code Templates. Review any custom templates defined in the 'Files', 'Includes', or 'Code' tabs. Also check Live Templates at Settings > Editor > Live Templates

Affected if Custom or third-party code templates are present in the configuration

The environment is affected if IntelliJ IDEA version is 2022.3.0 or earlier and custom code templates or live templates are configured in the IDE.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 2022.3.1 or later

Fixed in 2022.3.1

Interim mitigation

Upgrade IntelliJ IDEA to version 2022.3.1 or later to remediate the SSTI vulnerability in code Templates.

Recommended fix High confidence

2022.3.1 or later

Back up your IntelliJ IDEA settings and any important project configurations before upgrading
Download IntelliJ IDEA 2022.3.1 or later from the official JetBrains website (www.jetbrains.com)
Run the installer and choose the 'Overwrite' or 'Replace' installation option to replace the previous version
Complete the installation process
Launch IntelliJ IDEA and verify the version by navigating to Help > About
Re-import or re-open your projects as needed to ensure compatibility

Caveat IDE upgrades may temporarily affect plugin compatibility; review and update plugins as needed after upgrading

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
Testing1.0 h
Review / QA1.0 h

4.0 hours of engineering $750

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,200.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2022-47896 — 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

Primary sources

www.jetbrains.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2022-47896?

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.

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

At a glance

A fix existsUpgrade to 2022.3.1 or later

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Intellij Idea

Remediation

A high-priority fix

Fix this in Intellij Idea 4 hrs · Low

Typical engagement from $750

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2022-47896 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References