GitLabApplication
CVE-2020-13314
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. GitLab Omniauth endpoint allowed a malicious user to submit content to be displayed back to the user within error messages.
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 reflected XSS (cross-site scripting) vulnerability in GitLab's Omniauth authentication endpoint. A malicious user can submit crafted content that gets reflected back and displayed within error messages rendered to the victim. When the victim views these error messages, arbitrary JavaScript can execute in their browser context, potentially leading to session hijacking, cookie theft, or other client-side 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
GitLabApplication
>= 13.1.0, < 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Determine installed GitLab versionRun `sudo gitlab-rake gitlab:env:info` or check the version file at /opt/gitlab/version-manifest.txt, or access the Admin Dashboard and navigate to the Help section to view version informationAffected if Version is 13.1.0 through 13.1.9, 13.2.0 through 13.2.7, or 13.3.0 through 13.3.3
-
Verify if Omniauth is enabledInspect the GitLab configuration file at /etc/gitlab/gitlab.rb and look for the omniauth block, or access the GitLab Admin UI under Settings > Authentication (or /admin/application_settings#auth-settings)Affected if Omniauth is enabled with one or more providers configured
-
Confirm active Omniauth providersReview the omniauth.providers array in gitlab.rb or check the enabled authentication methods in the GitLab admin interface under the authentication settings sectionAffected if At least one external authentication provider (such as Google, GitHub, OAuth, SAML, or LDAP) is active
The environment is affected if GitLab version is within 13.1.0-13.1.9, 13.2.0-13.2.7, or 13.3.0-13.3.3 AND Omniauth authentication is enabled with at least one configured provider.
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. Alternatively, if immediate upgrade is not feasible, consider disabling or restricting Omniauth authentication methods until the patch can be applied.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13314 — 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-13314 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