dbcve.org
GitLabApplication

CVE-2019-9176

MEDIUM · 6.5 CVSS v3.0 Published 2019-04-17
Fix available
A fix is available. Upgrade to 11.6.10 / 11.7.6 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. It allows CSRF.

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

A Cross-Site Request Forgery (CSRF) vulnerability in GitLab Community and Enterprise Edition allows authenticated attackers to trick users into performing unintended actions by exploiting the lack of proper CSRF token validation in certain requests.

MitigationUpgrade GitLab to version 11.6.10, 11.7.6, 11.8.1 or later to receive the security patch that implements proper CSRF token validation.

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:< 11.6.10>= 11.7.0, < 11.7.6>= 11.8.0, < 11.8.1

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checks

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

  1. Identify if GitLab is installed
    Run 'gitlab-rake gitlab:env:info' or check for GitLab processes via 'ps aux | grep gitlab'
    Affected if GitLab is not found or the command fails, indicating GitLab is not present in the environment
  2. Determine installed GitLab version
    Run 'gitlab-rake gitlab:git:version' or check /opt/gitlab/embedded/service/gitlab-rails/VERSION file
    Affected if The command returns a version number that cannot be obtained, indicating GitLab may not be properly installed
  3. Compare version against affected ranges
    Parse the version number from step 2 and check if it falls into: < 11.6.10 OR (>= 11.7.0 AND < 11.7.6) OR (>= 11.8.0 AND < 11.8.1)
    Affected if The installed version matches any of these ranges: less than 11.6.10, between 11.7.0 and 11.7.5 inclusive, or exactly 11.8.0

A user is affected if their GitLab installation version falls within the vulnerable ranges: before 11.6.10, between 11.7.0-11.7.5, or exactly 11.8.0.

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 11.6.10 / 11.7.6 / 11.8.1 or later
Fixed in 11.6.1011.7.611.8.1
Interim mitigation

Upgrade GitLab to version 11.6.10, 11.7.6, 11.8.1 or later to receive the security patch that implements proper CSRF token validation.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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 locally
dbcve dependency scanner

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