dbcve.org
Intellij IdeaApplication · Jetbrains

CVE-2022-37009

HIGH · 7.8 CVSS v3.1 Published 2022-07-28
Fix available
A fix is available. Upgrade to 2022.2 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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.2 local code execution via a Vagrant executable 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 confidence

IntelliJ IDEA versions before 2022.2 allowed local code execution through the Vagrant executable integration. The IDE likely invokes Vagrant in an insecure manner, potentially allowing a local attacker to execute arbitrary code by manipulating Vagrantfile execution or the Vagrant command invocation.

MitigationUpgrade IntelliJ IDEA to version 2022.2 or later. Until then, avoid using the Vagrant integration features and ensure only trusted Vagrantfiles are used.

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.2

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
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? 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 installed IntelliJ IDEA version
    Open IntelliJ IDEA, go to Help > About (on Windows/Linux) or IntelliJ IDEA > About (on macOS). The version number is displayed in the dialog. Alternatively, check the installation directory or use system package management (e.g., 'winget list JetBrains.IntelliJIDEA' on Windows, 'ls /Applications' on macOS, or check /opt/ or ~/snap/ on Linux).
    Affected if The version displayed is any version earlier than 2022.2 (e.g., 2022.1, 2021.3, etc.) or if no version is shown (unrecognized installation).
  2. Verify Vagrant plugin is installed
    In IntelliJ IDEA, go to File > Settings > Plugins (or IntelliJ IDEA > Settings > Plugins on macOS). Search for 'Vagrant' in the Marketplace or Installed tabs.
    Affected if The Vagrant plugin is installed and enabled in a version before 2022.2.
  3. Confirm Vagrant executable is configured in IntelliJ
    Go to File > Settings > Tools > Vagrant (or IntelliJ IDEA > Settings > Tools > Vagrant). Check if a Vagrant executable path is configured and points to a Vagrant installation.
    Affected if A Vagrant executable path is configured and the IntelliJ version is below 2022.2.
  4. Check for Vagrantfile interaction
    Inspect the project for any Vagrantfile or .vagrant directory. In IntelliJ, check the Vagrant tool window (Vagrant > Vagrant Boxes) or look for Vagrant-related run configurations.
    Affected if Vagrantfiles are being managed or executed through IntelliJ in version below 2022.2.

The environment is affected if IntelliJ IDEA version is earlier than 2022.2 AND the Vagrant plugin is installed, enabled, or has been used to manage Vagrantfiles.

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.2 or later
Fixed in 2022.2
Interim mitigation

Upgrade IntelliJ IDEA to version 2022.2 or later. Until then, avoid using the Vagrant integration features and ensure only trusted Vagrantfiles are used.

Recommended fix High confidence

2022.2 or later

  1. Check the current IntelliJ IDEA version by navigating to Help > About
  2. Download IntelliJ IDEA 2022.2 or later from the official JetBrains website (www.jetbrains.com)
  3. Run the installer and follow the prompts to upgrade
  4. Restart IntelliJ IDEA after the upgrade completes
  5. Verify the installed version is 2022.2 or later via Help > About

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
  • Testing4.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,160
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,856.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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