GitLabApplication
CVE-2018-19570
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 11.3 before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1, are vulnerable to an XSS vulnerability in Markdown fields via unrecognized HTML tags.
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 CE/EE versions 11.3 before 11.3.11, 11.4 before 11.4.8, and 11.5 before 11.5.1 contain a stored Cross-Site Scripting (XSS) vulnerability in Markdown fields. The vulnerability allows injection of malicious scripts through unrecognized HTML tags that are not properly sanitized when rendered, potentially enabling session hijacking or data theft when users view crafted Markdown content.
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.3.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 versionLog into the GitLab instance as administrator and navigate to the Help > Version page, or query the API endpoint /api/v4/version, or run 'gitlab-rake gitlab:env:info' on the server command lineAffected if The displayed version falls within any of these ranges: 11.3.0 through 11.3.10, 11.4.0 through 11.4.7, or 11.5.0 through 11.5.0
-
Confirm Markdown rendering is enabledVerify that the GitLab Markdown feature is not disabled. Check the gitlab.yml configuration file (usually at /etc/gitlab/gitlab.yml) for the 'markdown' setting under the 'gitlab' section, or verify via the Admin Area > Application Settings > Markdown settingsAffected if Markdown processing is enabled (default state) and the version falls into the affected ranges above
-
Identify users with ability to create Markdown contentReview which users have permissions to create issues, merge requests, comments, or other content that supports Markdown formatting. This includes project members, external users with comment access, and anyone with write access to repositoriesAffected if Any untrusted or external users have the ability to submit Markdown-formatted content and the GitLab version is vulnerable
You are affected if your GitLab instance version is 11.3.0-11.3.10, 11.4.0-11.4.7, or 11.5.0-11.5.0 AND Markdown rendering is enabled, allowing any user with content creation permissions to inject malicious scripts via crafted HTML tags in Markdown fields.
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 to GitLab 11.3.11, 11.4.8, 11.5.1 or later. As an interim control, restrict or disable Markdown rendering for untrusted users until the upgrade is applied.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19570 — 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-19570 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