GitLabApplication
CVE-2020-13304
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 · uneditedA vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. Same 2 factor Authentication secret code was generated which resulted an attacker to maintain access under certain conditions.
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 confidenceGitLab before versions 13.1.10, 13.2.8, and 13.3.4 had a flaw in its 2FA implementation where the same authentication secret code was being generated. This predictability allowed attackers to potentially bypass 2FA and maintain unauthorized access to accounts under certain conditions.
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
< 13.1.10>= 13.2.0, < 13.2.8>= 13.3.0, < 13.3.4CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed GitLab versionNavigate to the GitLab admin area (Admin > Overview > Dashboard) or check the /etc/gitlab/gitlab.rb version file, or run `gitlab-rake gitlab:env:info` to display version informationAffected if The installed version is before 13.1.10, or between 13.2.0-13.2.7, or between 13.3.0-13.3.3
-
Confirm 2FA is enabledCheck if any users have Two-Factor Authentication (2FA) enabled in the GitLab instance by viewing the admin settings at Admin > Settings > Sign-up Restrictions, or by running `gitlab-ctl status` and checking user 2FA status via the API or admin interfaceAffected if 2FA is enabled for any user accounts in the GitLab instance
-
Verify TOTP secret generation behaviorThis vulnerability involves predictable TOTP secrets being generated during 2FA setup. If users in your environment set up 2FA during the affected versions, the generated secrets may have been predictable. Review any 2FA setup logs or consider if users recreated their 2FA during the affected version periodAffected if Users configured 2FA while running an affected GitLab version and may have used predictable TOTP secrets
You are affected if your GitLab version falls within the vulnerable ranges AND 2FA was enabled or configured while running an affected version, creating potentially predictable authentication secrets.
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 data13.1.1013.2.813.3.4
Upgrade GitLab to version 13.1.10, 13.2.8, 13.3.4 or later to receive the fix for the predictable 2FA secret generation vulnerability.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13304 — 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-13304 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