dbcve.org
GitLabApplication

CVE-2020-13325

HIGH · 7.1 CVSS v3.1 Published 2020-09-30
Fix available
A fix is available. Upgrade to 12.10.13 / 13.0.8 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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 prior 13.1. The comment section of the issue page was not restricting the characters properly, potentially resulting in a denial of service.

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

In GitLab versions prior to 13.1, the comment input field on issue pages lacked proper character validation, allowing specially crafted input to trigger a denial of service condition. This is an input validation failure that permits malformed or excessive characters to cause the application to become unresponsive or crash.

MitigationUpgrade GitLab to version 13.1 or later, which implements proper character restrictions on the issue comment field to prevent denial of service 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
Affected:>= 12.9.0, < 12.10.13>= 13.0.0, < 13.0.8>= 13.1.0, < 13.1.2

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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. Check installed GitLab version
    Run 'gitlab-rake gitlab:env:info' or check /opt/gitlab/version, or view the version in Admin Area > Settings > General > GitLab version
    Affected if Version is 12.9.0 through 12.10.12, or 13.0.0 through 13.0.7, or 13.1.0 through 13.1.1
  2. Verify issue comments feature is enabled
    Ensure the GitLab instance has issue tracking enabled and users can post comments on issues. This is a default-enabled feature in standard GitLab installations.
    Affected if Issue comments are accessible to users (the default configuration) and the version is within the affected ranges above

The environment is affected if the installed GitLab version falls within 12.9.0 to 12.10.12, 13.0.0 to 13.0.7, or 13.1.0 to 13.1.1 and the issue comment feature is accessible.

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.

From vendor data
Upgrade available Upgrade to 12.10.13 / 13.0.8 / 13.1.2 or later
Fixed in 12.10.1313.0.813.1.2
Interim mitigation

Upgrade GitLab to version 13.1 or later, which implements proper character restrictions on the issue comment field to prevent denial of service attacks.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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