dbcve.org
GitLabApplication

CVE-2022-2500

MEDIUM · 5.4 CVSS v3.1 Published 2022-08-05
Fix available
A fix is available. Upgrade to 15.0.5 / 15.1.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
A cross-site scripting issue has been discovered in GitLab CE/EE affecting all versions before 15.0.5, 15.1 prior to 15.1.4, and 15.2 prior to 15.2.1. A stored XSS flaw in job error messages allows 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 confidence

A stored XSS vulnerability in GitLab CI/CD job error messages allows attackers to inject malicious JavaScript that executes when other users view these messages, enabling session hijacking and actions on behalf of victims.

MitigationUpgrade GitLab to version 15.0.5 or later, 15.1.4 or later, or 15.2.1 or later to resolve the XSS in job error messages.

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.0.5>= 15.1.0, < 15.1.4= 15.2

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 GitLab version
    Navigate to Admin Area > Settings > General > GitLab configuration, or use the command: gitlab-rake gitlab:env:info
    Affected if The version is < 15.0.5, OR >= 15.1.0 and < 15.1.4, OR exactly 15.2.0
  2. Verify CI/CD pipelines are enabled
    Navigate to Admin Area > Settings > CI/CD > Runners, or check via API: GET /api/v4/pipelines
    Affected if CI/CD is enabled and pipelines can be created
  3. Check for existing pipeline jobs with error messages
    Go to a project's CI/CD > Pipelines > select a pipeline > view job output, or use API: GET /api/v4/projects/:id/jobs
    Affected if There are jobs with error messages visible to multiple users
  4. Determine user access to job error messages
    Navigate to Project > Settings > CI/CD > General pipelines settings, or review group/project member roles and pipeline visibility settings
    Affected if Multiple users (beyond the job owner) can view job error messages

You are affected if your GitLab version falls within the affected ranges AND CI/CD pipelines with error messages are accessible to users other than the job owner.

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.0.5 / 15.1.4 or later
Fixed in 15.0.515.1.4
Interim mitigation

Upgrade GitLab to version 15.0.5 or later, 15.1.4 or later, or 15.2.1 or later to resolve the XSS in job error messages.

Recommended fix High confidence

15.0.5, 15.1.4, or 15.2.1 (depending on your current major version)

  1. Identify your current GitLab version by navigating to the GitLab admin area or running `gitlab-rake gitlab:env:info`
  2. Download the appropriate fixed version (15.0.5, 15.1.4, or 15.2.1) from the official GitLab repository at https://about.gitlab.com/install/ce-or-ee/
  3. Back up your GitLab database and repositories before upgrading
  4. Follow the official GitLab upgrade documentation for your installation method (Omnibus or source)
  5. Upgrade to your chosen fixed version: 15.0.5 for pre-15.0.x installs, 15.1.4 for 15.1.x installs, or 15.2.1 for 15.2.x installs
  6. After upgrade, verify the installation by running `gitlab-rake gitlab:check`
  7. Confirm the XSS vulnerability is resolved by checking that job error messages no longer execute arbitrary JavaScript
Caveat Review GitLab 15.x release notes for any migration or compatibility notes before upgrading, and test in a staging environment first

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-2500 — 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-2500 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