CVE-2020-25013
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 ToolBox before version 1.18 is vulnerable to a Denial of Service attack via a browser protocol handler.
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 confidenceJetBrains ToolBox versions prior to 1.18 contain a vulnerability in their browser protocol handler that allows an attacker to trigger a Denial of Service condition. The vulnerability can be exploited by invoking the protocol handler in a way that causes the application to become unresponsive or crash.
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< 1.18CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Verify JetBrains Toolbox is installedCheck for the presence of JetBrains Toolbox application on the system. Common installation paths: Windows: %LOCALAPPDATA%\JetBrains\Toolbox\ or C:\Program Files\JetBrains\Toolbox\, macOS: /Applications/JetBrains Toolbox.app, Linux: ~/.local/share/JetBrains/Toolbox/ or /opt/jetbrains-toolbox/Affected if JetBrains Toolbox is not installed on the system
-
Determine installed version numberOpen JetBrains Toolbox, click the user menu (gear icon or username), select 'About' to view the version number. Alternatively, check the app executable file properties (right-click the .exe file > Properties > Details tab)Affected if The displayed version is any version prior to 1.18 (e.g., 1.17, 1.16, etc.)
-
Verify protocol handler is registeredCheck if the jetbrains:// protocol handler is registered on the system. On Windows: open Registry Editor and navigate to HKEY_CURRENT_USER\Software\Classes\jetbrains or search for 'jetbrains' in the registry. On macOS: run 'defaults read com.apple.LaunchServices | grep -i jetbrains' in Terminal. On Linux: check ~/.local/share/applications/ or /usr/share/applications/ for jetbrains-toolbox .desktop files containing the protocol schemeAffected if The jetbrains:// protocol handler is registered and enabled on the system
The system is affected if JetBrains Toolbox version 1.18 or later is not installed AND the jetbrains:// protocol handler is registered on the system.
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 data1.18
Update JetBrains ToolBox to version 1.18 or later to remediate this vulnerability.
- 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-2020-25013 — 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-2020-25013 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