CVE-2021-31901
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 · uneditedIn JetBrains Hub before 2021.1.13079, two-factor authentication wasn't enabled properly for the All Users group.
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 confidenceIn JetBrains Hub before version 2021.1.13079, the two-factor authentication mechanism failed to properly enforce 2FA requirements for users assigned to the All Users group. This authentication bypass allowed users in that group to access the system without completing 2FA verification, potentially exposing the application to credential theft 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< 2021.1.13079CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed JetBrains Hub versionCheck the Hub version by accessing the administration interface, looking at the startup logs, or querying the hub installation directory for a version file. Common locations: <hub_installation>/app/hub-version.txt or through the web UI footer.Affected if The installed version is earlier than 2021.1.13079 (e.g., 2021.1.x before 13079, or any 2020.x/2019.x release).
-
Confirm 2FA is enabled in HubLog in as an administrator, navigate to Administration > Authentication > Two-Factor Authentication, and verify that 2FA is turned on and configured for at least one user or group.Affected if 2FA is enabled and enforced for some users/groups but the 'All Users' group is NOT included in the 2FA requirement.
-
Inspect All Users group 2FA policyNavigate to Administration > Users and Groups > Groups > All Users, and check whether Two-Factor Authentication is listed as a requirement for this group.Affected if The All Users group exists but does NOT have 2FA enforcement enabled, while other groups do have 2FA enforcement.
-
Review authentication audit logsAccess Hub's audit or security logs (Administration > Security > Audit Log) and search for login events from users in the All Users group that completed authentication without 2FA verification.Affected if Logs show successful authentications from All Users group members that lack 2FA challenge completion timestamps.
You are affected if running any JetBrains Hub version below 2021.1.13079 AND you have 2FA enabled but the All Users group is not included in the 2FA enforcement policy.
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 data2021.1.13079
Upgrade JetBrains Hub to version 2021.1.13079 or later, then review and re-apply 2FA policies to ensure all user groups, including All Users, are properly covered by the authentication requirement.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-31901 — 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-2021-31901 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