dbcve.org
GitLabApplication

CVE-2022-1940

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-06
Fix available
A fix is available. Upgrade to 14.9.5 / 14.10.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable Patch available

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
A Stored Cross-Site Scripting vulnerability in Jira integration in GitLab EE affecting all versions from 13.11 prior to 14.9.5, 14.10 prior to 14.10.4, and 15.0 prior to 15.0.1 allows an attacker to execute arbitrary JavaScript code in GitLab on a victim's behalf via specially crafted Jira Issues

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
How this class of weakness works · CWE-79

Untrusted input is placed into a web page without being neutralised, so an attacker's markup or script executes in another user's browser. That can hijack sessions, capture keystrokes, or silently perform actions as the victim. Fixing it properly means context-aware output encoding everywhere data meets HTML, backed by a content-security policy as a second line of defence.

General guidance for the cross-site scripting (xss) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:>= 13.11.0, < 14.9.5>= 14.10.0, < 14.10.4= 15.0.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
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

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 14.9.5 / 14.10.4 or later
Fixed in 14.9.514.10.4
Vendor patch gitlab.com →
Recommended fix High confidence

Upgrade to GitLab 14.9.5, 14.10.4, 15.0.1 or later (15.x stable recommended)

  1. Identify your current GitLab version using the GitLab Rails console or the UI (Admin Area > Settings > General)
  2. Backup your GitLab database and repository data before upgrading
  3. Plan your upgrade path according to your current version - upgrade to 14.9.5, 14.10.4, or 15.0.1 or later
  4. For self-managed installations: Follow the official GitLab upgrade documentation for your package type (Omnibus or source)
  5. Stop GitLab services before upgrade if using source installation, or ensure Omnibus package handles this automatically
  6. Run the upgrade following GitLab's standard upgrade procedure: sudo gitlab-ctl restart for Omnibus or bundle exec rake gitlab:env:info RAILS_ENV=production for source
  7. After upgrade, verify GitLab is running and the Jira integration still functions correctly
  8. Confirm the vulnerability is patched by checking the GitLab version matches or exceeds 14.9.5, 14.10.4, or 15.0.1
Caveat Major version upgrades (e.g., 14.x to 15.x) may require additional migration steps and have longer downtime - review GitLab's upgrade documentation for breaking changes between versions

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $900. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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