CVE-2019-14960
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 · uneditedJetBrains Rider before 2019.1.2 was using an unsigned JetBrains.Rider.Unity.Editor.Plugin.Repacked.dll file.
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 confidenceJetBrains Rider before version 2019.1.2 shipped with an unsigned DLL file (JetBrains.Rider.Unity.Editor.Plugin.Repacked.dll). Unsigned binaries lack cryptographic verification, allowing potential attackers to replace the legitimate DLL with a malicious version through DLL planting or substitution attacks.
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< 2019.1.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check JetBrains Rider versionOpen JetBrains Rider and navigate to Help > About (or use the Rider version information in your system). Note the exact version number installed.Affected if The installed version is any version before 2019.1.2 (for example, 2019.1, 2019.1.1, 2018.x series)
-
Locate the Unity Editor Plugin DLLFind the file named JetBrains.Rider.Unity.Editor.Plugin.Repacked.dll in the JetBrains Rider installation directory, typically under the plugins or lib folder.Affected if The file exists in the installation directory and originates from an affected Rider version
-
Verify digital signature on the DLLUse a code signing verification tool (such as signtool.exe or PowerShell Get-AuthenticodeSignature) to inspect the digital signature status of JetBrains.Rider.Unity.Editor.Plugin.Repacked.dll.Affected if The DLL shows no digital signature or an invalid/invalidated signature (the file lacks cryptographic code signing)
-
Confirm vulnerability conditionIf both the version is below 2019.1.2 AND the DLL is unsigned, the environment is vulnerable to DLL planting or substitution attacks.Affected if JetBrains Rider version is below 2019.1.2 AND the Unity Editor Plugin DLL lacks a valid digital signature
A user is affected if they run JetBrains Rider versions prior to 2019.1.2 and the JetBrains.Rider.Unity.Editor.Plugin.Repacked.dll file in their installation lacks a valid digital signature.
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.
From vendor data2019.1.2
Update JetBrains Rider to version 2019.1.2 or later which includes proper code signing for the affected DLL.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14960 — 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-2019-14960 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