dbcve.org
GitLabApplication

CVE-2019-13121

HIGH · 7.5 CVSS v3.1 Published 2020-03-10
Fix available
A fix is available. Upgrade to after 12.0.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in GitLab Enterprise Edition 10.6 through 12.0.2. The GitHub project integration was vulnerable to an SSRF vulnerability which allowed an attacker to make requests to local network resources. It has Incorrect Access Control.

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 confidence

GitLab Enterprise Edition 10.6 through 12.0.2 contains an SSRF vulnerability in the GitHub project integration feature. The vulnerability allows remote attackers to make requests to internal/local network resources due to insufficient access controls on the integration, enabling potential reconnaissance and access to internal services.

MitigationUpgrade GitLab Enterprise Edition to a version beyond 12.0.2 that contains the security patch. Additionally, network segmentation and firewall rules can help limit the impact of SSRF attacks by restricting access to internal resources.

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
Affected:>= 10.6.0, <= 12.0.2

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab Admin Panel under Help > Version. Alternatively, check the installed package with `dpkg -l | grep gitlab-ee` (Debian) or `rpm -qa | grep gitlab-ee` (RHEL).
    Affected if The reported version is between 10.6.0 and 12.0.2 inclusive.
  2. Verify GitHub integration is accessible
    Log into GitLab as an administrator and navigate to Admin Area > Settings > Integrations. Look for the 'GitHub' integration in the list of available project integrations.
    Affected if The GitHub integration settings page is accessible and the integration can be configured.
  3. Confirm GitHub integration is enabled on any project
    Use the GitLab API or UI: go to a project Settings > Integrations and check if the GitHub integration is active. From the admin console, run: `curl -s "https://YOUR_GITLAB/api/v4/integrations" -H "PRIVATE-TOKEN: YOUR_TOKEN" | grep -i github` to list active integrations.
    Affected if The GitHub integration is enabled on at least one project.
  4. Check for outbound network requests
    Review GitLab logs for unusual outbound HTTP requests originating from the GitLab server during the time period the GitHub integration was used. Check access logs at `/var/log/gitlab/gitlab-rails/production.log` for requests to internal IP ranges (e.g., 10.x.x.x, 192.168.x.x, 127.0.0.1).
    Affected if Log entries show HTTP requests from the GitLab instance to internal/local network addresses triggered by the GitHub integration feature.

You are affected if your GitLab version falls within 10.6.0 to 12.0.2 AND the GitHub project integration feature is enabled on your instance.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 12.0.2
Interim mitigation

Upgrade GitLab Enterprise Edition to a version beyond 12.0.2 that contains the security patch. Additionally, network segmentation and firewall rules can help limit the impact of SSRF attacks by restricting access to internal resources.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-13121 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-13121 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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