CVE-2020-11691
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 2020.1.12099, content spoofing in the Hub OAuth error message was possible.
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 confidenceThis is a content spoofing vulnerability in JetBrains Hub's OAuth error message handling. Attackers could inject malicious content into error messages displayed during the OAuth authentication flow, potentially tricking users into trusting fraudulent messages or links. The vulnerability exists in versions prior to 2020.1.12099.
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< 2020.1.12099CVSS 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.
-
Locate JetBrains Hub installationIdentify where JetBrains Hub is installed on your system. Common locations include /opt/hub, /usr/local/hub, or C:\Program Files\JetBrains\Hub on Windows. Check for the hub directory containing the application files.Affected if JetBrains Hub is not present on the system, then this CVE does not apply.
-
Determine installed Hub versionCheck the version of your JetBrains Hub installation. Typically, this information is available in the Hub web interface under 'About' or 'Administration > Support', or by examining version files in the installation directory.Affected if The installed version is less than 2020.1.12099, placing it within the vulnerable range.
-
Verify OAuth authentication is enabledCheck if OAuth authentication is configured and enabled in your Hub installation. Inspect the authentication settings in the Hub administration panel or configuration files to determine whether OAuth providers are active.Affected if OAuth is not enabled or configured, the content spoofing vulnerability in OAuth error handling would not be exploitable in your environment.
-
Review OAuth provider configurationExamine the OAuth-related configuration files or settings in Hub to understand which OAuth providers are configured and how error messages are handled during the authentication flow.Affected if OAuth is enabled and the version is below 2020.1.12099, your environment is affected by this content spoofing vulnerability.
You are affected if JetBrains Hub is installed with a version prior to 2020.1.12099 and OAuth authentication is enabled.
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 data2020.1.12099
Upgrade JetBrains Hub to version 2020.1.12099 or later to patch the content spoofing vulnerability in OAuth error handling.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11691 — 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-11691 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