GitLabApplication
CVE-2017-0915
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.2.4 is vulnerable to a lack of input validation in the GitlabProjectsImportService 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 confidenceGitLab Community Edition 10.2.4 contains an input validation flaw in the GitlabProjectsImportService that allows remote attackers to inject and execute arbitrary code through the project import functionality.
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.9.0, <= 9.5.10>= 10.0.0, <= 10.1.5>= 10.2.0, <= 10.2.5>= 10.3.0, <= 10.3.3
Debian LinuxOperating system
= 9.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed GitLab versionRun 'gitlab-rake gitlab:env:info' or check /opt/gitlab/version to obtain the exact version numberAffected if The installed version falls within any of these ranges: 8.9.0-9.5.10, 10.0.0-10.1.5, 10.2.0-10.2.5, or 10.3.0-10.3.3
-
Confirm project import is accessibleLog in as an administrator, go to Admin Area > Settings > General > Visibility and access controls, and verify whether project import from external sources is enabled for usersAffected if Project import functionality is enabled and accessible to regular users or untrusted accounts
-
Review recent import activityCheck Git logs and application logs (/var/log/gitlab/gitlab-rails/production.log) for project import requests, looking for unusual file names or API calls from the /api/v4/projects/import endpointAffected if There are import requests from untrusted sources or suspicious import payloads in the logs
You are affected if your GitLab version is in the vulnerable range AND the project import feature is accessible to users who should not have code execution capabilities.
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.
dbcve · scopedUpgrade to a patched GitLab version. Until then, restrict or disable the project import feature for untrusted users and monitor for suspicious import activity.
GitLab 10.3.4 (or latest 10.3.x); for other affected branches: 9.5.11, 10.1.6, or 10.2.6 respectively
- 1. Back up your GitLab instance and database before upgrading
- 2. Identify your current GitLab version by running `gitlab-rake gitlab:env:info`
- 3. For GitLab 10.3.x: Upgrade to version 10.3.4 or later (recommended: 10.3.4)
- 4. For GitLab 10.2.x: Upgrade to version 10.2.6 or later
- 5. For GitLab 10.0.x-10.1.x: Upgrade to version 10.1.6 or later
- 6. For GitLab 9.x: Upgrade to version 9.5.11 or later
- 7. After upgrade, verify the version with `gitlab-rake gitlab:env:info`
- 8. Review GitLab release notes for any post-upgrade migration tasks
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0915 — 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-0915 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