GitLabApplication
CVE-2020-10980
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 EE/CE 8.0.rc1 to 12.9 is vulnerable to a blind SSRF in the FogBugz integration.
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 confidenceA blind Server-Side Request Forgery (SSRF) vulnerability exists in GitLab's FogBugz integration from version 8.0.rc1 through 12.9. An attacker can exploit this to make the GitLab server perform arbitrary HTTP requests to internal or external resources without proper URL validation, potentially accessing internal services, cloud metadata endpoints, or performing network reconnaissance.
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.0.0, <= 12.9CVSS 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 your GitLab versionNavigate to the GitLab Admin area (e.g., /admin) and check the version number displayed on the dashboard, or run `gitlab-rake gitlab:env:info` from the server console to retrieve the exact version.Affected if The installed version is 8.0.0 through 12.9 inclusive
-
Locate the FogBugz integration settingsIn GitLab, go to either Project Settings > Integrations (for project-level) or Admin Area > Applications > Integrations (for system-level) and look for FogBugz in the list of available integrations.Affected if The FogBugz integration appears in the available integrations list and is listed as active or enabled
-
Verify if FogBugz integration is enabledExamine the FogBugz integration entry to determine if the 'Active' checkbox is ticked or if the integration status shows as enabled. Check both global admin-level and individual project-level integration settings.Affected if The FogBugz integration is active, has a configured FogBugz project URL, or shows an enabled/active status
You are affected if your GitLab version is 8.0.0 through 12.9 AND the FogBugz integration is enabled or has been configured at any point.
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 GitLab to version 12.10 or later. If immediate upgrade is not feasible, disable or restrict the FogBugz integration until the patch can be applied.
GitLab 12.9.1 or later (12.10.x, 13.x stable releases)
- Check your current GitLab version using `gitlab-rake gitlab:env:info` or the GitLab admin area
- Review the FogBugz integration settings in GitLab admin area under Project Settings > Integrations and disable FogBugz if not needed
- Upgrade to GitLab 12.9.1 or later which contains the security fix for this SSRF vulnerability
- After upgrade, verify FogBugz integration is functioning correctly if still required
- Ensure network segmentation is in place to prevent exploited SSRF from reaching internal services
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
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10980 — 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-10980 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