GitLabApplication
CVE-2017-0927
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 Edition version 10.3 is vulnerable to an improper authorization issue in the deployment keys component resulting in unauthorized use of deployment keys by guest users.
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 confidenceGitLab Community Edition 10.3 contains a broken access control vulnerability in the deployment keys component. Guest users, who should have minimal read-only access to public projects, can improperly use deployment keys that should be restricted to higher-privileged users. This allows unauthorized access to repositories via deployment keys.
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
>= 8.16.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed GitLab versionRun `gitlab-rake gitlab:env:info` or check the GitLab admin dashboard under /admin/application_settings for the exact version numberAffected if The installed version falls within any of these ranges: 8.16.0-9.5.10, 10.0.0-10.1.5, 10.2.0-10.2.5, or 10.3.0-10.3.3
-
Identify guest usersIn GitLab admin area, navigate to Users and filter by guest access level, or run: `gitlab-rake gitlab:git:fsck` to verify repository access and check user roles via admin panelAffected if Any guest user accounts exist in the GitLab instance
-
Verify deployment keys are configuredNavigate to the admin dashboard /admin/deploy_keys or check project settings for deploy keys. Run: `curl -s --header "PRIVATE-TOKEN: <your-token>" https://gitlab.example.com/api/v4/deploy_keys | jq`Affected if Deployment keys are created and associated with projects
-
Confirm public projects with guest accessCheck for public projects that have guest users added as members. In GitLab admin, filter projects by visibility level public and review member access listsAffected if Public projects exist where guest users have been granted any level of access
You are affected if your GitLab version is in the vulnerable range AND you have deployment keys in use alongside guest users accessing public projects.
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 version 10.4 or later, which contains the fix for proper authorization checks on deployment keys. If immediate upgrade is not possible, review and restrict guest user permissions and consider disabling deployment keys until the patch can be applied.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0927 — 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-0927 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