dbcve.org
GitLabApplication

CVE-2022-3513

MEDIUM · 6.1 CVSS v3.1 Published 2023-04-05
Fix available
A fix is available. Upgrade to 15.8.5 / 15.9.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 affecting all versions starting from 12.8 before 15.8.5, all versions starting from 15.9 before 15.9.4, all versions starting from 15.10 before 15.10.1. A specially crafted payload could lead to a reflected XSS on the client side which allows attackers to perform arbitrary actions on behalf of victims on 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 reflected cross-site scripting (XSS) vulnerability in GitLab allows attackers to inject malicious scripts through specially crafted payloads. The attack is reflected back to the victim's browser, enabling session hijacking and arbitrary actions on behalf of authenticated users. Self-hosted instances without strict Content Security Policy (CSP) headers are vulnerable.

MitigationUpgrade GitLab to version 15.8.5, 15.9.4, or 15.10.1 or later. Implement strict Content Security Policy headers as a defense-in-depth measure.

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:>= 12.8.0, < 15.8.5>= 15.9.0, < 15.9.4= 15.10.0

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

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

  1. Identify installed GitLab version
    Run command: sudo gitlab-rake gitlab:env:info | grep -i version or check /opt/gitlab/version
    Affected if Version falls within < 15.8.5, 15.9.0 to < 15.9.4, or = 15.10.0 ranges (also includes >= 12.8.0)
  2. Compare version against affected ranges
    Compare the discovered version number to the affected ranges: 12.8.0 to 15.8.4, 15.9.0 to 15.9.3, or 15.10.0 exactly
    Affected if Installed version matches any of the vulnerable version ranges
  3. Verify Content Security Policy configuration
    Check GitLab admin settings for CSP headers: navigate to Admin Area > Settings > General > Content Security Policy, or inspect response headers for 'Content-Security-Policy' directive
    Affected if No strict CSP headers are configured or CSP is disabled

User is affected if their GitLab version is 12.8.0 to 15.8.4, 15.9.0 to 15.9.3, or exactly 15.10.0 AND no strict Content Security Policy headers are enforced.

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.8.5 / 15.9.4 or later
Fixed in 15.8.515.9.4
Interim mitigation

Upgrade GitLab to version 15.8.5, 15.9.4, or 15.10.1 or later. Implement strict Content Security Policy headers as a defense-in-depth measure.

Recommended fix High confidence

Upgrade to 15.8.5, 15.9.4, or 15.10.1 (whichever is the next stable release in your current version branch)

  1. 1. Identify the currently running GitLab version using `gitlab-rake gitlab:env:info` or the GitLab admin interface.
  2. 2. Based on the current version, determine the appropriate upgrade target: for 12.8.x-15.7.x upgrade to 15.8.5; for 15.9.x upgrade to 15.9.4; for 15.10.0 upgrade to 15.10.1.
  3. 3. Before upgrading, backup the GitLab database and repositories using `gitlab-backup-create` or the omnibus backup tool.
  4. 4. Update the GitLab package repository and upgrade using `sudo apt-get update && sudo apt-get install gitlab-ce` (Debian/Ubuntu) or `sudo yum install gitlab-ce` (RHEL/CentOS).
  5. 5. After installation, run `sudo gitlab-ctl reconfigure` to apply configuration changes.
  6. 6. Verify the upgrade was successful by checking the version with `gitlab-rake gitlab:env:info` or accessing the admin dashboard.
  7. 7. Confirm the reflected XSS vulnerability is no longer present by verifying the fix is applied in the relevant component.
Caveat Major version upgrades (e.g., 12.x to 15.x) may require additional migration steps and downtime; review the GitLab upgrade documentation for specific version path requirements

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3513 — 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-3513 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