dbcve.org
GitLabApplication

CVE-2019-19313

HIGH · 7.5 CVSS v3.1 Published 2020-01-05
Fix available
A fix is available. Upgrade to 12.3.8 / 12.4.5 or later.
See remediation →
84/100
Remediation priority · High
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
GitLab EE 12.3 through 12.5, 12.4.3, and 12.3.6 allows Denial of Service. Certain characters were making it impossible to create, edit, or view issues and commits.

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 confidence

GitLab EE versions 12.3 through 12.5, 12.4.3, and 12.3.6 contain a denial of service vulnerability where certain characters in issue titles, descriptions, or commit messages cause the application to become unresponsive or crash when attempting to create, edit, or view these objects.

MitigationUpgrade GitLab EE to a version beyond 12.5 that contains the patched character handling routines; test issue and commit creation with special characters to verify the fix.

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.3.0, < 12.3.8>= 12.4.0, < 12.4.5>= 12.5.0, < 12.5.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Determine installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check the version file at `/opt/gitlab/version`
    Affected if The version falls within 12.3.0 to 12.3.7, 12.4.0 to 12.4.4, or 12.5.0 to 12.5.1 (EE edition)
  2. Verify GitLab web interface is operational
    Attempt to access the GitLab web application via HTTP/HTTPS on the configured hostname
    Affected if The web interface responds, indicating the application is running and accessible
  3. Confirm issue tracking is enabled
    Check if any projects exist with the issues module active by reviewing project settings or attempting to access an issue via the web UI or API
    Affected if Projects with issue tracking enabled exist and are accessible through the web interface or API

You are affected if GitLab EE version is 12.3.0-12.3.7, 12.4.0-12.4.4, or 12.5.0-12.5.1 and the web interface with issue or repository features 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.3.8 / 12.4.5 / 12.5.2 or later
Fixed in 12.3.812.4.512.5.2
Interim mitigation

Upgrade GitLab EE to a version beyond 12.5 that contains the patched character handling routines; test issue and commit creation with special characters to verify the fix.

Fix this in GitLab Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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