GitLabApplication
CVE-2018-19574
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 CE/EE, versions 7.6 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 XSS vulnerability in the OAuth authorization page.
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 confidenceGitLab CE/EE versions 7.6 through 11.x before specific patched releases contain a cross-site scripting (XSS) vulnerability in the OAuth authorization page. The OAuth authorization flow does not properly sanitize user-supplied input, allowing authenticated attackers to inject malicious scripts that execute in the context of other users' sessions.
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
>= 7.6.0, < 11.3.11>= 11.4.0, < 11.4.8>= 11.5.0, < 11.5.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed GitLab versionRun 'gitlab-rake gitlab:env:info' or check /opt/gitlab/embedded/service/gitlab-rails/VERSION on the GitLab serverAffected if The version displayed falls within any of these ranges: 7.6.0 to 11.3.10, 11.4.0 to 11.4.7, or 11.5.0 to 11.5.0
-
Verify OAuth is enabledNavigate to Admin Area > Application Settings > OAuth or check the gitlab.yml configuration file for oauth configurationAffected if OAuth single sign-on is enabled and users can initiate OAuth authorization flows
-
Check if GitLab instance uses external OAuth providersReview /etc/gitlab/gitlab.rb for omniauth configurations or check Admin Area > OmniAuth providersAffected if One or more external OAuth providers (Google, GitHub, GitLab.com, etc.) are configured as login methods
-
Confirm user-facing OAuth authorization page is accessibleAttempt to access the OAuth authorization endpoint by initiating an OAuth flow with a configured provider, or review routing for /oauth/authorizeAffected if The OAuth authorization endpoint responds and displays an authorization consent page to users
An environment is affected if it runs a vulnerable GitLab version (7.6.0-11.3.10, 11.4.0-11.4.7, or 11.5.0-11.5.0) AND has OAuth authentication enabled, allowing users to authorize third-party applications through the OAuth flow.
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.
From vendor data11.3.1111.4.811.5.1
Upgrade GitLab to version 11.3.11, 11.4.8, or 11.5.1 or later to remediate this vulnerability.
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-2018-19574 — 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-2018-19574 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