GitLabApplication
CVE-2020-10956
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 8.10 and later through 12.9 is vulnerable to an SSRF in a project import note feature.
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 confidenceGitLab versions 8.10 through 12.9 contain a Server-Side Request Forgery (SSRF) vulnerability in the project import note feature. This allows an attacker to make the GitLab server perform arbitrary requests to internal or external resources by manipulating the import note 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.10.0, < 12.9.1CVSS 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.1/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 versionAccess the GitLab admin area or check the /opt/gitlab/version file, or run 'gitlab-rake gitlab:env:info' to display version informationAffected if The version is 8.10.0 through 12.9.0 (inclusive)
-
Verify project import feature accessibilityConfirm whether the project import functionality is available on the GitLab instance. Check if users with appropriate permissions can access the project import featureAffected if The project import feature is enabled and accessible to users
-
Check for project import from URL functionalityReview if the project import feature allows importing from a URL, which is the attack vector for this SSRF vulnerabilityAffected if The import from URL option is available in the import functionality
The environment is affected if the installed GitLab version falls between 8.10.0 and 12.9.0 inclusive AND the project import feature with URL import capability is accessible on the instance
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 · scoped12.9.1
Upgrade GitLab to version 12.9.1 or later, which contains the patched version of the affected component.
12.9.1 or later (recommended: latest stable 12.x or newer)
- 1. Back up your GitLab instance data and configuration before upgrading
- 2. Check your current GitLab version (typically via `gitlab-rake gitlab:env:info` or checking the admin area)
- 3. For Omnibus installations: update the package repository with `apt-get update` or `yum check-update`
- 4. For Omnibus installations: upgrade GitLab with `apt-get install gitlab-ce` or `yum install gitlab-ce` (or gitlab-ee depending on your edition)
- 5. For installations from source: follow the official upgrade guide for your target version
- 6. Run `gitlab-ctl reconfigure` to apply configuration changes
- 7. Verify the upgrade was successful and GitLab is functioning properly
- 8. Confirm the version is now 12.9.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10956 — 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-2020-10956 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