dbcve.org
GitLabApplication

CVE-2022-3573

MEDIUM · 5.4 CVSS v3.1 Published 2023-01-12
Fix available
A fix is available. Upgrade to 15.5.7 / 15.6.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.4 before 15.5.7, all versions starting from 15.6 before 15.6.4, all versions starting from 15.7 before 15.7.2. Due to the improper filtering of query parameters in the wiki changes page, an attacker can execute arbitrary JavaScript on the self-hosted instances running without strict CSP.

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 confidence

A stored Cross-Site Scripting (XSS) vulnerability in GitLab's wiki changes page allows attackers to inject malicious JavaScript via improperly filtered query parameters. The vulnerability is exploitable on self-hosted GitLab instances that do not enforce a strict Content Security Policy (CSP), enabling arbitrary script execution in the context of other users' sessions.

MitigationUpgrade GitLab to version 15.5.7, 15.6.4, 15.7.2 or later. As an additional defense-in-depth measure, ensure strict Content Security Policy headers are enabled on the GitLab instance.

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
Affected:>= 15.4.0, < 15.5.7>= 15.6.0, < 15.6.4>= 15.7.0, < 15.7.2
Drive ComposerApplication
Affected:<= 2.8

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed GitLab version
    Run command: `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area at /admin/application_settings under 'Metrics and profiling' section showing version information
    Affected if The displayed version falls within: >= 15.4.0 and < 15.5.7, OR >= 15.6.0 and < 15.6.4, OR >= 15.7.0 and < 15.7.2
  2. Verify wiki feature is accessible
    Navigate to any project wiki page on the GitLab instance and verify the wiki functionality is enabled for at least one user or group
    Affected if Wiki pages are accessible and users can create or edit wiki content; the stored XSS only affects instances where the wiki feature is active
  3. Check Content Security Policy configuration
    Inspect HTTP response headers from the GitLab instance by running: `curl -I https://your-gitlab-instance.com` and look for Content-Security-Policy header
    Affected if The CSP header is missing, weak, or does not include `script-src` restrictions; a strict CSP can mitigate XSS impact even on vulnerable versions

If the GitLab version falls within the affected ranges AND the wiki feature is enabled, the instance is vulnerable; a strict CSP header provides defense-in-depth mitigation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 15.5.7 / 15.6.4 / 15.7.2 or later
Fixed in 15.5.715.6.415.7.2
Interim mitigation

Upgrade GitLab to version 15.5.7, 15.6.4, 15.7.2 or later. As an additional defense-in-depth measure, ensure strict Content Security Policy headers are enabled on the GitLab instance.

Recommended fix High confidence

15.5.7, 15.6.4, or 15.7.2 (depending on which version branch you're upgrading from)

  1. 1. Identify the currently running GitLab version by checking the GitLab administration area or running 'gitlab-rake gitlab:env:info'
  2. 2. Based on your current version, determine the appropriate upgrade target: if running 15.4.x-15.5.x, upgrade to 15.5.7 or later; if running 15.6.x, upgrade to 15.6.4 or later; if running 15.7.0-15.7.1, upgrade to 15.7.2 or later
  3. 3. Review the GitLab upgrade documentation for your current version to the target version
  4. 4. Perform a backup of the GitLab database and repositories before upgrading
  5. 5. Follow the standard GitLab upgrade procedure for your installation method (omnibus, source, or Helm chart)
  6. 6. After upgrade, verify the GitLab version matches the fixed release
  7. 7. Test the wiki functionality to confirm the XSS fix is applied
Caveat Standard GitLab upgrade risks apply - review release notes for deprecations and ensure compatibility with your integration ecosystem

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3573 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3573 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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