GitLabApplication
CVE-2021-22227
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 · uneditedA reflected cross-site script vulnerability in GitLab before versions 13.11.6, 13.12.6 and 14.0.2 allowed an attacker to send a malicious link to a victim and trigger actions on their behalf if they clicked it
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 confidenceA reflected cross-site scripting (XSS) vulnerability in GitLab versions prior to 13.11.6, 13.12.6, and 14.0.2 allowed attackers to inject malicious scripts into URLs. When authenticated users clicked these crafted links, the script executed within their session context, enabling unauthorized actions on their behalf.
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
< 13.11.6>= 13.12.0, < 13.12.6>= 14.0.0, < 14.0.2CVSS 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 versionRun command: gitlab-rake gitlab:env:info or check the GitLab admin panel at /admin/application_settings under 'GitLab version'Affected if The displayed version falls within < 13.11.6, >= 13.12.0 to < 13.12.6, or >= 14.0.0 to < 14.0.2
-
Verify version is within affected rangeCompare the installed version number to the affected ranges: any version below 13.11.6, between 13.12.0-13.12.5, or between 14.0.0-14.0.1 is vulnerableAffected if Installed version matches any of the three affected version ranges
-
Confirm GitLab service is runningVerify the GitLab instance is operational by accessing the web interface or checking service status with systemctl status gitlab-runsvdir or similarAffected if GitLab is running and accessible to users who could be targeted by the XSS
The environment is affected if the running GitLab version is any version prior to 13.11.6, between 13.12.0-13.12.5, or between 14.0.0-14.0.1, and users authenticate to the instance.
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 data13.11.613.12.614.0.2
Upgrade GitLab to version 13.11.6, 13.12.6, 14.0.2 or later. As a reflected XSS, the primary defense is patching the vulnerable endpoint(s) to properly sanitize or encode user-supplied input before reflecting it in responses.
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-2021-22227 — 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-2021-22227 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