GitLabApplication
CVE-2018-19493
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 · uneditedAn issue was discovered in GitLab Community and Enterprise Edition 11.x before 11.3.11, 11.4.x before 11.4.8, and 11.5.x before 11.5.1. There is a persistent XSS vulnerability in the environment pages due to a lack of input validation and output encoding.
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 confidenceGitLab Community and Enterprise Edition versions 11.x before 11.3.11, 11.4.x before 11.4.8, and 11.5.x before 11.5.1 contain a stored (persistent) cross-site scripting (XSS) vulnerability in the environment pages. The vulnerability stems from insufficient input validation and lack of proper output encoding when handling environment-related data, allowing attackers to inject malicious scripts that execute in the browsers of other users viewing the affected pages.
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
>= 11.0.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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-ctl version' or check the GitLab Admin Area > About page to find the exact version numberAffected if The version is 11.0.0 to 11.3.10, 11.4.0 to 11.4.7, or 11.5.0 to 11.5.0 (any version in the ranges >= 11.0.0 and < 11.3.11, >= 11.4.0 and < 11.4.8, or >= 11.5.0 and < 11.5.1)
-
Verify GitLab editionConfirm whether you are running GitLab Community Edition (CE) or Enterprise Edition (EE) - both CE and EE versions in the affected ranges are vulnerableAffected if Running CE or EE versions within the vulnerable ranges listed above
-
Check if CI/CD environments feature is accessibleNavigate to a project with CI/CD enabled and verify the ability to create or view environments under CI/CD > Environments, or check if the /environments routes are accessibleAffected if The environments feature is present and accessible - the XSS flaw exists in this environment pages functionality
You are affected if your GitLab version falls within 11.0.0-11.3.10, 11.4.0-11.4.7, or 11.5.0-11.5.0 and the CI/CD environments feature is enabled and accessible in your installation.
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. As a compensating control, implement strict input validation and output encoding for all user-supplied data in environment pages.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19493 — 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-19493 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