dbcve.org
GitLabApplication

CVE-2017-0916

CRITICAL · 9.8 CVSS v3.0 Published 2018-03-21
Fix available
A fix is available. Upgrade to after 10.3.3 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
Gitlab Community Edition version 10.3 is vulnerable to a lack of input validation in the system_hook_push queue through web hook component resulting in remote code execution.

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 CE 10.3 lacks input validation in the system_hook_push queue when processing web hook data, allowing attackers to inject malicious code through the web hook component that executes on the GitLab server.

MitigationImplement strict input validation and sanitization on all web hook data entering the system_hook_push queue; upgrade to a patched GitLab version.

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:>= 8.8.0, <= 10.1.5>= 10.2.0, <= 10.2.5>= 10.3.0, <= 10.3.3
Debian LinuxOperating system
Affected:= 9.0

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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. Verify GitLab is installed
    Run 'gitlab-rake gitlab:env:info' or check for GitLab installation directories such as /opt/gitlab, /var/opt/gitlab, or /home/git/gitlab
    Affected if GitLab is not installed, the system is not affected by this CVE
  2. Determine the installed GitLab version
    Run 'gitlab-rake gitlab:git:version' or check /opt/gitlab/embedded/service/gitlab-rails/VERSION file, or use the GitLab admin dashboard at /admin/application_settings
    Affected if The installed version falls within any of these ranges: >= 8.8.0 and <= 10.1.5, OR >= 10.2.0 and <= 10.2.5, OR >= 10.3.0 and <= 10.3.3
  3. Confirm web hooks are enabled
    Check the GitLab admin panel at /admin/hooks or run 'curl -s http://localhost/api/v3/hooks' with appropriate admin credentials to list configured web hooks
    Affected if No web hooks are configured or enabled, the attack surface does not exist for this specific vulnerability
  4. Verify the system_hook_push queue exists
    Check Redis for the presence of the system_hook_push queue by running 'redis-cli LLEN resque:queue:system_hook_push' if Redis is accessible, or examine GitLab sidekiq configuration files for queue definitions
    Affected if The system_hook_push queue is present and actively processing hook events, the vulnerability is exploitable in the environment

The environment is affected if GitLab CE versions 8.8.0-10.1.5, 10.2.0-10.2.5, or 10.3.0-10.3.3 are installed AND web hooks are enabled with the system_hook_push queue in use.

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 a release after 10.3.3
Interim mitigation

Implement strict input validation and sanitization on all web hook data entering the system_hook_push queue; upgrade to a patched GitLab version.

Recommended fix High confidence

GitLab 10.3.4 or later (or upgrade to a stable release beyond 10.3.x)

  1. 1. Back up your GitLab database and repository data before proceeding with any upgrade.
  2. 2. For GitLab installations using the official omnibus packages, update your package index: sudo apt-get update
  3. 3. Install the updated GitLab package: sudo apt-get install gitlab-ce (or gitlab-ee for Enterprise Edition)
  4. 4. Reconfigure GitLab to apply the changes: sudo gitlab-ctl reconfigure
  5. 5. Verify the upgrade was successful by checking the GitLab version at /help or running: sudo gitlab-rake gitlab:env:info
  6. 6. Ensure the GitLab service is running properly: sudo gitlab-ctl status
Caveat Upgrading GitLab across major versions may require reading release notes for database migrations and configuration changes; test in staging first

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

Fix this in GitLab Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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