dbcve.org
GitLabApplication

CVE-2019-9174

CRITICAL · 10.0 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 →
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
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 SSRF.

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

A Server-Side Request Forgery (SSRF) vulnerability in GitLab Community and Enterprise Edition versions before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1 allows attackers to make the GitLab server make arbitrary HTTP requests to internal or external resources, potentially accessing sensitive internal services.

MitigationUpgrade GitLab to version 11.6.10, 11.7.6, or 11.8.1 or later. If immediate upgrade is not possible, restrict outbound network access from the GitLab server and monitor for suspicious internal requests.

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or look at the GitLab admin dashboard under /help or the version file at /opt/gitlab/version-manifest.txt
    Affected if The displayed version is below 11.6.10, OR between 11.7.0 and 11.7.5 inclusive, OR between 11.8.0 and 11.8.0 inclusive
  2. Verify GitLab service is running
    Run `sudo gitlab-ctl status` to confirm the GitLab web service is active
    Affected if GitLab is running and the version falls into the affected ranges from step 1
  3. Confirm web hook or integration features are accessible
    Check if users can create web hooks or project integrations by navigating to Project Settings > Integrations or reviewing the gitlab.yml configuration at /opt/gitlab/embedded/service/gitlab-rails/config/gitlab.yml
    Affected if The GitLab instance has web hooks, integrations, or any feature that can trigger outbound HTTP requests enabled, and the version is affected

You are affected if your GitLab installation version is 11.6.x below 11.6.10, 11.7.x below 11.7.6, or 11.8.x below 11.8.1 and the web service is active with external request features 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.

dbcve · scoped
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, or 11.8.1 or later. If immediate upgrade is not possible, restrict outbound network access from the GitLab server and monitor for suspicious internal requests.

Recommended fix High confidence

GitLab 11.8.1 or later

  1. Back up your GitLab instance database and configuration files
  2. Determine your current GitLab version by running `sudo gitlab-rake gitlab:env:info`
  3. For versions < 11.6.10: upgrade directly to 11.6.10 or later
  4. For versions 11.7.0-11.7.5: upgrade to 11.7.6 or later
  5. For versions 11.8.0: upgrade to 11.8.1 or later
  6. Follow the official GitLab upgrade documentation for your installation method (Omnibus, source, or Docker)
  7. Run `sudo gitlab-ctl reconfigure` after upgrade if using Omnibus
  8. Verify the upgrade was successful with `sudo gitlab-rake gitlab:check`
Caveat Check GitLab 11.8.1 release notes for breaking changes specific to your deployment

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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