GitLabApplication
CVE-2018-17454
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 before 11.1.7, 11.2.x before 11.2.4, and 11.3.x before 11.3.1. There is stored XSS on the issue details screen.
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 confidenceA stored cross-site scripting (XSS) vulnerability in GitLab Community and Enterprise Edition allows attackers to inject malicious JavaScript into issue content. This script executes in the browsers of other users who view the affected issue details screen.
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.1.7>= 11.2.0, < 11.2.4= 11.3.0CVSS 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.
-
Identify the installed GitLab versionAccess the GitLab Admin area by navigating to the GitLab instance and looking for the version information typically displayed in the Admin dashboard, or use the GitLab command line/API (for example, checking the /api/v4/version endpoint or running 'gitlab-rake gitlab:env:info')Affected if The version falls within < 11.1.7, OR >= 11.2.0 and < 11.2.4, OR equals 11.3.0
-
Confirm the GitLab instance uses the issue tracking featureVerify that issue tracking is enabled on the GitLab instance by navigating to the project settings or checking if any projects have issues createdAffected if Issue tracking is active and users can create or view issues in any project
-
Identify if any issues contain suspicious contentReview recent issues in the GitLab web interface, particularly the issue title and description fields, looking for unexpected script tags, event handlers, or other JavaScript code that may have been injectedAffected if Issues exist that contain unescaped HTML or JavaScript in their content fields that could execute in a user's browser when viewed
A user is affected if their GitLab version is 11.1.x below 11.1.7, 11.2.x below 11.2.4, or exactly 11.3.0, AND the issue tracking feature is in use with potentially malicious content present in issues.
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.
dbcve · scoped11.1.711.2.4
Upgrade GitLab to version 11.1.7, 11.2.4, 11.3.1 or later to remediate this stored XSS vulnerability.
GitLab 11.3.1 (or minimum 11.1.7 for 11.1.x, 11.2.4 for 11.2.x)
- 1. Back up your GitLab instance data and configuration
- 2. Review GitLab upgrade documentation for your current version
- 3. Plan maintenance window as upgrade may require downtime
- 4. Upgrade to GitLab 11.3.1 (or minimum 11.1.7 or 11.2.4 depending on your branch)
- 5. After upgrade, verify GitLab is functioning correctly
- 6. Test that the issue details screen renders correctly and XSS is no longer present
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17454 — 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-17454 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