dbcve.org
ResharperApplication · Jetbrains

CVE-2019-16407

HIGH · 7.3 CVSS v3.1 Published 2019-10-02
Fix available
A fix is available. Upgrade to 2019.2 or later.
See remediation →
73/100
Remediation priority · Elevated

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
JetBrains ReSharper installers for versions before 2019.2 had a DLL Hijacking vulnerability.

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

JetBrains ReSharper installers before version 2019.2 contained a DLL hijacking vulnerability. The installer likely loaded DLLs from insecure paths, allowing an attacker with local write access to place a malicious DLL that would be executed with elevated privileges during the installation process.

MitigationUpgrade to ReSharper version 2019.2 or later, which contains the patched installer that addresses the DLL hijacking vulnerability.

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
ResharperApplication
Affected:< 2019.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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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 ReSharper version
    Open Visual Studio and navigate to ReSharper > Help > About, or check Windows Programs and Features for JetBrains ReSharper
    Affected if The version displayed is below 2019.2
  2. Verify version from installation folder
    Locate the ReSharper installation directory (typically C:\Program Files\JetBrains\ReSharper\) and check version.txt or the folder name for the version number
    Affected if The version found is 2019.1 or earlier

If the installed ReSharper version is 2019.1 or earlier, the environment was likely affected by the DLL hijacking vulnerability in the installer used to deploy it

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.

From vendor data
Upgrade available Upgrade to 2019.2 or later
Fixed in 2019.2
Interim mitigation

Upgrade to ReSharper version 2019.2 or later, which contains the patched installer that addresses the DLL hijacking vulnerability.

Fix this in Resharper Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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