GitLabApplication
CVE-2019-12442
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 Enterprise Edition 11.7 through 11.11. The epic details page contained a lack of input validation and output encoding issue which resulted in a persistent XSS vulnerability on child epics.
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 persistent XSS vulnerability exists in GitLab Enterprise Edition 11.7-11.11 on the epic details page. The application fails to properly validate input and encode output when handling child epics, allowing attackers to inject malicious JavaScript that executes in the browsers of other users viewing those epics.
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.7.0, <= 11.11.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/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 versionAccess the GitLab admin area or run `gitlab-rake gitlab:env:info` to display version information. Alternatively, check the footer of any GitLab page which typically displays the version number.Affected if The displayed version falls within the range 11.7.0 to 11.11.0 inclusive.
-
Confirm GitLab edition is Enterprise EditionVerify that the installed product is GitLab Enterprise Edition (EE), not Community Edition (CE). This is typically visible in the admin dashboard or on the license page.Affected if The edition shows as Enterprise Edition and the version is 11.7.0 to 11.11.0.
-
Verify epics module is enabledNavigate to the GitLab admin settings and confirm that the epics feature is enabled for the instance. Epics are only available in Enterprise Edition.Affected if Epics are enabled and the GitLab version is 11.7.0 to 11.11.0.
-
Inspect existing epics for unexpected contentReview epics that have child epics assigned to them. Examine the child epic titles and descriptions for any unusual characters, script tags, or encoded content that could represent XSS payloads.Affected if Any child epic contains unsanitized HTML or JavaScript that would execute when the epic details page is viewed.
A user is affected if they are running GitLab Enterprise Edition version 11.7.0 through 11.11.0 with the epics feature enabled.
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 dataUpgrade GitLab Enterprise Edition to version 11.12 or later to receive the security patch, or apply the available GitLab security patch for 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-2019-12442 — 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-2019-12442 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