dbcve.org
GitLabApplication

CVE-2022-2235

MEDIUM · 5.4 CVSS v3.1 Published 2022-07-01
Fix available
A fix is available. Upgrade to 14.10.5 / 15.0.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
Insufficient sanitization in GitLab EE's external issue tracker affecting all versions from 14.5 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 allows an attacker to perform cross-site scripting when a victim clicks on a maliciously crafted ZenTao link

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

This is a stored XSS vulnerability in GitLab EE's external issue tracker integration with ZenTao. Due to insufficient input sanitization when processing ZenTao links, attackers can inject malicious JavaScript that executes when victims click on crafted links in the issue tracker.

MitigationUpgrade GitLab to version 14.10.5, 15.0.4, or 15.1.1 or later to remediate the insufficient sanitization in the external issue tracker.

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:>= 14.5.0, < 14.10.5>= 15.0.0, < 15.0.4= 15.1.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

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. Check your GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under /help for the exact version number
    Affected if The installed version falls within 14.5.0 to 14.10.4, 15.0.0 to 15.0.3, or is exactly 15.1.0
  2. Verify if ZenTao integration is enabled
    Navigate to GitLab admin area, go to Settings > Integrations, and check if the ZenTao external issue tracker is configured with a URL
    Affected if ZenTao is configured as an external issue tracker in the project or group settings
  3. Inspect external issue tracker links for suspicious patterns
    Review the issue tracker URL configuration in project settings under Project Settings > Integrations > ZenTao; examine any stored URLs for encoded characters or script tags
    Affected if The ZenTao URL contains unexpected JavaScript event handlers, script tags, or encoded payloads that suggest injection
  4. Review audit logs for issue tracker modifications
    Check GitLab audit logs under Admin Area > Audit Events or project audit logs for any changes to the ZenTao integration configuration
    Affected if Audit logs show unexpected modifications to the external issue tracker settings by unauthorized users

You are affected if your GitLab version is in the vulnerable range AND the ZenTao external issue tracker integration is enabled with a potentially malicious URL configured.

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 14.10.5 / 15.0.4 or later
Fixed in 14.10.515.0.4
Interim mitigation

Upgrade GitLab to version 14.10.5, 15.0.4, or 15.1.1 or later to remediate the insufficient sanitization in the external issue tracker.

Recommended fix High confidence

Upgrade to GitLab 14.10.5, 15.0.4, or 15.1.1 (or later) - recommended: 15.1.1 or latest stable

  1. Back up your GitLab instance data and configuration before proceeding with the upgrade
  2. Update your GitLab package repository to fetch the latest available packages
  3. For Debian/Ubuntu systems: run 'apt-get update' then 'apt-get install gitlab-ce' (or 'gitlab-ee' depending on your edition)
  4. For RHEL/CentOS systems: run 'yum install gitlab-ce' (or 'gitlab-ee')
  5. After installation, run 'gitlab-ctl reconfigure' to apply the updates
  6. Verify the GitLab version matches the expected patched release using 'gitlab-rake gitlab:env:info'
  7. Test that the external issue tracker integration works correctly to confirm the XSS fix is applied
Caveat Review GitLab release notes for any breaking changes between your current version and target version; minor upgrades within the same major.minor typically have low risk

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

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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