GitLabApplication
CVE-2017-0914
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 · uneditedGitlab Community and Enterprise Editions version 10.1, 10.2, and 10.2.4 are vulnerable to a SQL injection in the MilestoneFinder component resulting in disclosure of all data in a GitLab instance's database.
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 confidenceSQL injection vulnerability in the MilestoneFinder component of GitLab Community and Enterprise Editions versions 10.1, 10.2, and 10.2.4 allows attackers to inject malicious SQL queries, enabling unauthorized disclosure of all data in the GitLab instance's database.
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
>= 9.4.0, <= 9.5.10>= 10.0.0, <= 10.1.5>= 10.2.0, <= 10.2.5>= 10.3.0, <= 10.3.3CVSS 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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check GitLab version via command lineRun 'gitlab-rake gitlab:env:info' or 'gitlab --version' to retrieve the installed GitLab versionAffected if The displayed version falls within >= 9.4.0 to <= 9.5.10, >= 10.0.0 to <= 10.1.5, >= 10.2.0 to <= 10.2.5, or >= 10.3.0 to <= 10.3.3
-
Check GitLab version via web interfaceNavigate to the GitLab admin area (usually /admin) and locate the version information displayed on the dashboard or in the 'Overview' sectionAffected if The displayed version matches any of the affected ranges listed above
-
Verify MilestoneFinder component is accessibleConfirm that the Milestones feature is enabled for any project on the GitLab instance by navigating to a project settings or attempting to access the milestones page (usually /milestones)Affected if The Milestones feature is active and users can interact with milestone search functionality
-
Check for SQL injection indicators in logsExamine GitLab production logs (typically in /var/log/gitlab/gitlab-rails/production.log) for unusual SQL patterns or errors in milestone-related queriesAffected if Logs contain malformed SQL queries or database errors referencing the MilestoneFinder component
The environment is affected if the installed GitLab version falls within any of the four vulnerable ranges AND the Milestones feature is accessible to users.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade GitLab to a patched version beyond 10.2.4 that addresses this SQL injection vulnerability in the MilestoneFinder component.
Fix this in GitLab
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0914 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-0914 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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