dbcve.org
HubApplication · Jetbrains

CVE-2021-25759

MEDIUM · 6.5 CVSS v3.1 Published 2021-02-03
Fix available
A fix is available. Upgrade to 2020.1.12629 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 2020.1.12629, an authenticated user can delete 2FA settings of any other user.

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

This is a broken access control vulnerability in JetBrains Hub where an authenticated user can delete two-factor authentication settings of any other user due to missing authorization checks. The flaw allows privilege escalation by enabling a regular user to modify security settings of other accounts.

MitigationUpgrade JetBrains Hub to version 2020.1.12629 or later which contains the authorization fix. Alternatively, review and enforce proper access control checks on all user settings endpoints.

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:< 2020.1.12629

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 application in your environment and confirm it is running.
    Affected if JetBrains Hub is present in the environment
  2. Determine installed version
    Check the Hub version by accessing the administration interface or reviewing version metadata files.
    Affected if Version is below 2020.1.12629
  3. Verify authentication is enabled
    Confirm that user authentication is configured and users can log in to Hub.
    Affected if Authentication is enabled and regular users have access
  4. Check user settings endpoints
    Review access control configuration on user profile and security settings endpoints.
    Affected if No proper authorization checks exist on 2FA management endpoints for cross-user modifications

You are affected if JetBrains Hub version is below 2020.1.12629 and user authentication is enabled, allowing any authenticated user to modify 2FA settings of other accounts.

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

Upgrade JetBrains Hub to version 2020.1.12629 or later which contains the authorization fix. Alternatively, review and enforce proper access control checks on all user settings endpoints.

Fix this in Hub Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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