GitLabApplication
CVE-2020-13292
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 GitLab before 13.0.12, 13.1.6 and 13.2.3, it is possible to bypass E-mail verification which is required for OAuth Flow.
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 confidenceThis vulnerability allows bypassing email verification during the OAuth authentication flow in GitLab. An attacker could potentially associate unverified emails with their OAuth account or bypass verification checks meant to ensure users control the email address they're authenticating with.
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
GitLabApplication
>= 12.3.0, < 13.0.12>= 13.1.0, < 13.1.6>= 13.2.0, < 13.2.3CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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 GitLab versionRun 'gitlab-rake gitlab:env:info' from the GitLab server command line, or check the Admin area under Settings > Metrics and Monitoring to retrieve the exact GitLab version numberAffected if Version is 12.3.0 or later but earlier than 13.0.12, OR 13.1.0 through 13.1.5, OR 13.2.0 through 13.2.2
-
Confirm OAuth authentication is enabledNavigate to the GitLab Admin area, go to Settings > Authentication and Authorization, and check if any OAuth providers (such as Google, GitHub, GitLab.com, or custom OAuth) are configured and activeAffected if One or more OAuth sign-in sources are enabled and users can authenticate using OAuth
Environment is affected if GitLab version falls within the listed vulnerable ranges AND OAuth authentication providers are configured and active.
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.
dbcve · scoped13.0.1213.1.613.2.3
Upgrade GitLab to version 13.0.12, 13.1.6, 13.2.3 or later to apply the patch for this OAuth email verification bypass.
13.0.12, 13.1.6, or 13.2.3 (or latest stable 13.2.x+)
- Back up your GitLab instance data before upgrading
- Upgrade GitLab to version 13.0.12 (if on 12.x), 13.1.6 (if on 13.1.x), or 13.2.3 (if on 13.2.x)
- Alternatively, upgrade to the latest stable version (13.2.4 or later) which contains the fix
- After upgrade, verify the OAuth flow email verification is working correctly
- Review GitLab release notes for any additional changes in the target version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13292 — 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-13292 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