dbcve.org
GitLabApplication

CVE-2020-13312

CRITICAL · 9.8 CVSS v3.1 Published 2020-09-14
Fix available
A fix is available. Upgrade to 13.1.10 / 13.2.8 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. GitLab OAuth endpoint was vulnerable to brute-force attacks through a specific parameter.

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

GitLab's OAuth implementation contains a vulnerability where a specific parameter on the OAuth endpoint is susceptible to brute-force attacks. An attacker could exploit this by making repeated requests with different values to guess or cycle through authentication tokens, potentially leading to unauthorized access to user accounts via the OAuth flow.

MitigationUpgrade GitLab to version 13.1.10, 13.2.8, 13.3.4 or later. These versions contain the fix for the OAuth brute-force vulnerability.

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
Affected:>= 13.1.0, < 13.1.10>= 13.2.0, < 13.2.8>= 13.3.0, < 13.3.4

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

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed GitLab version
    Run 'gitlab-rake gitlab:env:info' or check /opt/gitlab/embedded/service/gitlab-rails/VERSION file. Alternatively, access GitLab Admin area > Help > Version to see the exact version.
    Affected if Version is 13.1.0-13.1.9, 13.2.0-13.2.7, or 13.3.0-13.3.3 (falls within the affected ranges)
  2. Confirm OAuth is enabled
    Check if OAuth integration is configured. Look in /etc/gitlab/gitlab.rb for 'gitlab_rails[\'omniauth_enabled\'] = true' or access Admin Area > Settings > Authentication and verify any OAuth providers are enabled.
    Affected if OAuth is enabled and at least one OAuth provider is configured (GitLab, Google, GitHub, etc.)
  3. Check for brute-force attempt logs
    Search GitLab logs in /var/log/gitlab/gitlab-rails/ production.log for repeated POST requests to /oauth/authorize endpoint with varying 'state' or 'code' parameters. Use: grep -i 'oauth/authorize' production.log | grep -c 'IP_ADDRESS' to identify unusual request volumes.
    Affected if High volume of OAuth authorization requests from single IP or repeated failed token attempts visible in logs

You are affected if your GitLab version falls within 13.1.0 to 13.1.9, 13.2.0 to 13.2.7, or 13.3.0 to 13.3.3 AND OAuth authentication is enabled with one or more providers configured.

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.

dbcve · scoped
Upgrade available Upgrade to 13.1.10 / 13.2.8 / 13.3.4 or later
Fixed in 13.1.1013.2.813.3.4
Interim mitigation

Upgrade GitLab to version 13.1.10, 13.2.8, 13.3.4 or later. These versions contain the fix for the OAuth brute-force vulnerability.

Recommended fix High confidence

13.3.4 or later (latest stable GitLab release)

  1. 1. Back up your GitLab instance data before proceeding with the upgrade.
  2. 2. Review the GitLab upgrade documentation for your installation method (Omnibus, source, or Docker).
  3. 3. Plan for downtime during the upgrade process.
  4. 4. Upgrade GitLab to version 13.3.4 or later (recommended: latest stable 13.x release).
  5. 5. Verify the upgrade was successful by accessing the GitLab instance.
  6. 6. Confirm the OAuth functionality works correctly after the upgrade.
Caveat Upgrading across multiple minor versions (e.g., 13.1.x to 13.3.x) may introduce breaking changes; review the GitLab release notes for each intermediate version.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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