dbcve.org
RiderApplication · Jetbrains

CVE-2022-37396

HIGH · 7.8 CVSS v3.1 Published 2022-08-03
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 Rider before 2022.2 Trust and Open Project dialog could be bypassed, leading to local code execution

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

In JetBrains Rider before version 2022.2, the Trust and Open Project dialog security mechanism could be bypassed, allowing potentially malicious project files to execute code locally without user consent or proper security review.

MitigationUpgrade to JetBrains Rider 2022.2 or later to obtain the patch that enforces the Trust and Open Project dialog properly.

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
RiderApplication
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. Determine installed JetBrains Rider version
    Open JetBrains Rider, go to Help > About (or use the command line: rider --version if available). Note the full version number displayed.
    Affected if The displayed version is any build number below 2022.2 (e.g., 2022.1.x, 2021.3.x, etc.)
  2. Verify the specific build number
    In the About dialog, locate the build number (e.g., 222.3345.31). Compare this numeric build against the 2022.2 release build.
    Affected if The build number corresponds to a release prior to the 2022.2 stable release
  3. Confirm the Trust and Open Project feature exists
    In the affected versions, this dialog appears when opening projects from untrusted locations. The vulnerability allows bypassing this prompt.
    Affected if The dialog exists in the installed version (it was introduced in earlier 2022.x releases and present through 2022.1)

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 to JetBrains Rider 2022.2 or later to obtain the patch that enforces the Trust and Open Project dialog properly.

Recommended fix High confidence

2022.2

  1. Download JetBrains Rider 2022.2 or later from the official JetBrains website (www.jetbrains.com)
  2. Close any running instances of JetBrains Rider
  3. Install the downloaded version of Rider, following the installation prompts
  4. After installation, restart Rider and verify the version is 2022.2 or later

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

Fix this in Rider Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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