dbcve.org
GitLabApplication

CVE-2018-20499

HIGH · 7.2 CVSS v3.1 Published 2019-12-30
Fix available
A fix is available. Upgrade to 11.4.13 / 11.5.6 or later.
See remediation →
81/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 Community and Enterprise Edition before 11.x before 11.4.13, 11.5.x before 11.5.6, and 11.6.x before 11.6.1. It allows SSRF.

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 confidence

Server-Side Request Forgery (SSRF) vulnerability in GitLab Community and Enterprise Edition allows an attacker to make the GitLab server perform requests to attacker-controlled destinations, potentially accessing internal services or infrastructure.

MitigationUpgrade GitLab to version 11.4.13, 11.5.6, 11.6.1 or later to receive the vendor patch for this SSRF vulnerability.

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:>= 11.0.0, < 11.4.13>= 11.5.0, < 11.5.6>= 11.6.0, < 11.6.1

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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. Check installed GitLab version via command line
    Run `cat /opt/gitlab/version` for Omnibus installations, or `cat /home/git/gitlab/version` for source installations, or use `gitlab-rake gitlab:env:info` to display version details.
    Affected if The displayed version falls within 11.0.0 to 11.4.12, 11.5.0 to 11.5.5, or equals 11.6.0.
  2. Check GitLab version via web UI
    Log in as an administrator, navigate to the Admin Area (wrench icon) and scroll to the GitLab version section found on the overview page, or go to Help > Version.
    Affected if The version shown is within the affected ranges specified above.
  3. Verify exact version number
    Confirm the full version string including any patch numbers (for example, 11.4.12-ee or 11.5.0-ee). GitLab uses -ee for Enterprise Edition and -ce for Community Edition.
    Affected if The precise version number is less than 11.4.13, 11.5.6, or 11.6.1 respectively for each branch.

You are affected if your GitLab installation runs any version from 11.0.0 up to 11.4.12, 11.5.0 up to 11.5.5, or exactly 11.6.0.

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 11.4.13 / 11.5.6 / 11.6.1 or later
Fixed in 11.4.1311.5.611.6.1
Interim mitigation

Upgrade GitLab to version 11.4.13, 11.5.6, 11.6.1 or later to receive the vendor patch for this SSRF vulnerability.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-20499 — 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-2018-20499 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