GitLabApplication
CVE-2022-2904
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 cross-site scripting issue has been discovered in GitLab CE/EE affecting all versions starting from 15.2 before 15.2.5, all versions starting from 15.3 before 15.3.4, all versions starting from 15.4 before 15.4.1 It was possible to exploit a vulnerability in the external status checks feature which could lead to a stored XSS that allowed attackers to perform arbitrary actions on behalf of victims at client side.
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 exists in GitLab's external status checks feature across versions 15.2.x (before 15.2.5), 15.3.x (before 15.3.4), and 15.4.x (before 15.4.1). Attackers can inject malicious scripts that execute in victim browsers, enabling unauthorized actions to be performed on behalf of authenticated users.
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
>= 15.2, < 15.2.5>= 15.2, <= 15.2.5>= 15.3, < 15.3.4>= 15.3, <= 15.3.4= 15.4CVSS 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 installed GitLab versionLog into GitLab as admin and navigate to the Admin Area > Overview > Dashboard, or run 'gitlab-rake gitlab:env:info' to retrieve the exact version numberAffected if Version is 15.2.x before 15.2.5, 15.3.x before 15.3.4, or 15.4.x before 15.4.1 (versions 15.2.0-15.2.4, 15.3.0-15.3.3, or 15.4.0)
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 · scoped15.2.515.3.4
Upgrade GitLab to version 15.4.1 or later (or to 15.3.4/15.2.5 for respective branches) to apply the security patch. Review external status checks configurations for any malicious payloads that may have been injected.
15.2.5, 15.3.4, or 15.4.1 (depending on your current minor version)
- 1. Back up your GitLab database and configuration files before proceeding with the upgrade
- 2. Identify your current GitLab version by running `gitlab-rake gitlab:env:info`
- 3. If running 15.2.x: upgrade to 15.2.5 as the minimum fixed version
- 4. If running 15.3.x: upgrade to 15.3.4 as the minimum fixed version
- 5. If running 15.4.x: upgrade to 15.4.1 as the minimum fixed version
- 6. For self-managed installations, follow the official GitLab upgrade documentation for your package type (Omnibus or source)
- 7. After upgrade, verify the version with `gitlab-rake gitlab:env:info`
- 8. Test the external status checks functionality to confirm the fix works correctly
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-2022-2904 — 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-2022-2904 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