dbcve.org
HubApplication · Jetbrains

CVE-2021-36209

CRITICAL · 9.8 CVSS v3.1 Published 2021-08-06
Fix available
A fix is available. Upgrade to 2021.1.13389 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Hub before 2021.1.13389, account takeover was possible during password reset.

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 confidence

In JetBrains Hub before version 2021.1.13389, a vulnerability in the password reset mechanism allowed attackers to take over user accounts. The flaw likely involved improper validation of password reset tokens or insufficient authorization checks during the reset process, enabling unauthorized password changes for any user.

MitigationUpgrade JetBrains Hub to version 2021.1.13389 or later to remediate the account takeover vulnerability in the password reset flow.

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
HubApplication
Affected:< 2021.1.13389

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify JetBrains Hub installation
    Locate the JetBrains Hub installation directory or check running services on the system. Common locations include /opt/hub, /usr/local/hub, or as a Docker container. Look for the hub startup script or JAR files.
    Affected if JetBrains Hub is installed on the system
  2. Determine installed Hub version
    Check the version file or startup banner. If running from command line, look for version output (e.g., ./hub --version) or check the about/version page in the web interface at /about. Alternatively, check the JAR file name or contents if installed locally.
    Affected if Unable to determine version or version is visible
  3. Compare version to affected range
    Compare the installed version number to the affected range: versions before 2021.1.13389 are vulnerable. Note the exact version string format used by your installation (e.g., 2021.1.12345 or similar).
    Affected if Installed version is less than 2021.1.13389 (e.g., 2021.1.13000, 2021.1, 2020.x, etc.)
  4. Verify password reset is accessible
    Check if the Hub web interface is accessible and the password reset functionality is enabled. Access the login page and confirm a password reset option exists. This is the vulnerable component that could be exploited.
    Affected if Password reset feature is exposed and accessible to unauthenticated users

The environment is affected if JetBrains Hub is installed and its version is lower than 2021.1.13389, with the password reset mechanism accessible for exploitation.

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 2021.1.13389 or later
Fixed in 2021.1.13389
Interim mitigation

Upgrade JetBrains Hub to version 2021.1.13389 or later to remediate the account takeover vulnerability in the password reset flow.

Recommended fix High confidence

2021.1.13389

  1. Identify the current version of JetBrains Hub running in your environment
  2. If the version is below 2021.1.13389, plan for an upgrade to version 2021.1.13389 or later
  3. Back up the Hub database and configuration files before performing the upgrade
  4. Download the updated Hub installation package from the official JetBrains distribution
  5. Stop the Hub service or ensure no active sessions during the upgrade
  6. Install the updated Hub version (2021.1.13389 or newer)
  7. Verify the upgrade was successful by checking the new version number
  8. Test the password reset functionality to confirm the vulnerability is remediated

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

Fix this in Hub 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-2021-36209 — 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-2021-36209 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