dbcve.org
GitLabApplication

CVE-2018-19569

HIGH · 8.8 CVSS v3.0 Published 2019-07-10
Fix available
A fix is available. Upgrade to 11.3.11 / 11.4.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
GitLab CE/EE, versions 8.8 up to 11.x before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1, are vulnerable to an authorization vulnerability that allows access to the web-UI as a user using a Personal Access Token of any scope.

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

This is an authorization bypass vulnerability in GitLab where Personal Access Tokens (PATs) of any scope can be used to authenticate to the web-UI as the associated user, allowing access to functionality that should be restricted based on token scope.

MitigationUpgrade GitLab to versions 11.3.11, 11.4.8, 11.5.1 or later. Alternatively, restrict web-UI access by disabling token-based web authentication or implementing additional access controls.

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:>= 8.8.0, < 11.3.11>= 11.4.0, < 11.4.8>= 11.5.0, < 11.5.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Determine installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check `/opt/gitlab/version` (Omnibus), or look at the web interface footer for the version number
    Affected if Version falls within any of these ranges: 8.8.0 to 11.3.10, 11.4.0 to 11.4.7, or 11.5.0 to 11.5.0
  2. Confirm GitLab package version
    Check the installed package version via package manager: `rpm -q gitlab-ee` or `dpkg -l | grep gitlab`
    Affected if Package version matches the affected version ranges above
  3. Verify PAT authentication method is in use
    Review whether Personal Access Tokens are being used for authentication in your environment by checking user configurations or API access patterns
    Affected if PATs are used and GitLab version is within the affected ranges listed

A user is affected if their GitLab installation version is 8.8.0 up to 11.3.10, 11.4.0 up to 11.4.7, or 11.5.0 up to 11.5.0, and they use Personal Access Tokens for authentication.

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.3.11 / 11.4.8 / 11.5.1 or later
Fixed in 11.3.1111.4.811.5.1
Interim mitigation

Upgrade GitLab to versions 11.3.11, 11.4.8, 11.5.1 or later. Alternatively, restrict web-UI access by disabling token-based web authentication or implementing additional access controls.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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