dbcve.org
GitLabApplication · Jenkins

CVE-2022-34777

MEDIUM · 5.4 CVSS v3.1 Published 2022-06-30
Fix available
A fix is available. Upgrade to after 1.5.34 or later.
See remediation →
58/100
Remediation priority · Elevated
High EPSS 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
Jenkins GitLab Plugin 1.5.34 and earlier does not escape multiple fields inserted into the description of webhook-triggered builds, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.

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

Jenkins GitLab Plugin versions 1.5.34 and earlier fail to properly escape multiple fields before inserting them into the description of webhook-triggered builds. This allows stored XSS attacks where malicious JavaScript is rendered when users view build descriptions.

MitigationUpgrade Jenkins GitLab Plugin to a patched version (if available) or implement output encoding/escaping on all fields inserted into build descriptions.

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:<= 1.5.34

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. Identify GitLab Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, locate GitLab Plugin, and note the version number displayed. Alternatively, check the plugin manifest file (META-INF/MANIFEST.MF) within the gitlab-plugin.hpi file in the plugins directory.
    Affected if The installed version is 1.5.34 or earlier.
  2. Confirm webhook integration is active
    Navigate to the GitLab configuration page (typically under Manage Jenkins > Configure System > GitLab) and verify that a GitLab connection is configured and enabled for one or more jobs.
    Affected if GitLab webhook triggers are configured and actively creating builds.
  3. Inspect recent build descriptions for unsanitized content
    Review build history for jobs using GitLab webhooks. Navigate to specific build pages and view the build description. Look for HTML/script tags, encoded characters, or content that appears to be unsanitized user input from GitLab (such as branch names, commit messages, or merge request titles).
    Affected if Build descriptions contain raw HTML, script tags, or clearly unescaped special characters that originated from GitLab webhook payloads.

You are affected if the GitLab Plugin version is 1.5.34 or earlier AND webhooks are configured to trigger builds, allowing unsanitized webhook data to render as executable script in build descriptions.

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 a release after 1.5.34
Interim mitigation

Upgrade Jenkins GitLab Plugin to a patched version (if available) or implement output encoding/escaping on all fields inserted into build descriptions.

Recommended fix Moderate confidence

GitLab Plugin 1.5.35 or later

  1. 1. Navigate to Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Click on the 'Installed' tab
  4. 4. Find the 'GitLab Plugin' in the list
  5. 5. If an update is available, check the plugin and click 'Update'
  6. 6. Alternatively, download GitLab Plugin version 1.5.35 or later from the Jenkins plugin repository
  7. 7. Restart Jenkins if required to complete the installation

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