dbcve.org
List Git Branches ParameterApplication · Jenkins

CVE-2022-27212

MEDIUM · 5.4 CVSS v3.1 Published 2022-03-15
Fix available
A fix is available. Upgrade to after 0.0.9 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
Jenkins List Git Branches Parameter Plugin 0.0.9 and earlier does not escape the name of the 'List Git branches (and more)' parameter, 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

The Jenkins List Git Branches Parameter Plugin versions 0.0.9 and earlier fails to escape the name parameter in the 'List Git branches (and more)' feature. This allows a stored XSS payload injected into the parameter name to execute in the browsers of other users who view the affected parameter, requiring attackers to have Item/Configure permissions.

MitigationUpgrade the List Git Branches Parameter Plugin to a version newer than 0.0.9 that includes proper output encoding, or restrict Item/Configure permissions to trusted users only until a patch is available.

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
List Git Branches ParameterApplication
Affected:<= 0.0.9

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 if List Git Branches Parameter plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed, or run this in the script console: Jenkins.instance.pluginManager.plugins.find{it.shortName == 'list-git-branches-parameter'}?.version
    Affected if Plugin is installed and the version returned is 0.0.9 or lower (or version cannot be determined, indicating an old installation)
  2. Identify jobs using the vulnerable parameter
    Search job configuration XML files or use the Jenkins script console to find jobs containing '<listGitBranchesParameter>' or the parameter type 'List Git Branches (and more)': Jenkins.instance.allItems.collect{job -> [name: job.fullName, config: job.configFile.asXml()]}.findAll{it.config.contains('listGitBranchesParameter')}
    Affected if Any job is configured to use the 'List Git Branches (and more)' parameter type from this plugin
  3. Verify permission assignments for job configuration
    Review which users or groups have Item/Configure permission (or Overall/Administer for older Jenkins versions) by checking job-based security settings in job configuration pages or via script: Jenkins.instance.allItems.collect{i -> [name: i.fullName, permissions: i.authorizationMatrixProperty?.getGrantedPermissions()]}
    Affected if Users other than fully trusted administrators have Item/Configure permissions on jobs using this plugin

You are affected if the List Git Branches Parameter plugin version 0.0.9 or earlier is installed AND any job uses the 'List Git Branches (and more)' parameter AND untrusted users have Item/Configure permission on those jobs.

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 0.0.9
Interim mitigation

Upgrade the List Git Branches Parameter Plugin to a version newer than 0.0.9 that includes proper output encoding, or restrict Item/Configure permissions to trusted users only until a patch is available.

Recommended fix Moderate confidence

List Git Branches Parameter Plugin 0.0.10 or later

  1. Navigate to Jenkins Manage Plugins page
  2. Go to the 'Available' tab and search for 'List Git Branches Parameter' plugin
  3. If an update is available, select the plugin and click 'Download now and install after restart'
  4. Alternatively, go to 'Installed' tab, find the plugin, and check for updates
  5. After updating, restart Jenkins to complete the installation
  6. Verify the plugin version is updated to a version newer than 0.0.9

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

Fix this in List Git Branches Parameter Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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