dbcve.org
CredentialsApplication · Jenkins

CVE-2022-29036

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-12
Fix available
A fix is available. Upgrade to 2.6.1.1 / 1074.1076.v39c30cecb_0e2 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 Credentials Plugin 1111.v35a_307992395 and earlier, except 1087.1089.v2f1b_9a_b_040e4, 1074.1076.v39c30cecb_0e2, and 2.6.1.1, does not escape the name and description of Credentials parameters on views displaying parameters, 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

A stored cross-site scripting (XSS) vulnerability in Jenkins Credentials Plugin versions 1111.v35a_307992395 and earlier allows attackers with Item/Configure permission to inject malicious scripts through the name and description fields of Credentials parameters, which are not properly escaped when rendered on view pages.

MitigationUpdate Jenkins Credentials Plugin to version 1087.1089.v2f1b_9a_b_040e4, 1074.1076.v39c30cecb_0e2, 2.6.1.1, or any later patched version to remediate the XSS vulnerability.

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
CredentialsApplication
Affected:< 2.6.1.1>= 1055.v1346ba467ba1, < 1074.1076.v39c30cecb_0e2>= 1105.vb_4e24a_c78b_81, < 1112.vc87b_7a_3597f6

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 Jenkins Credentials Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Credentials' plugin, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep credentials
    Affected if The installed version falls into any of these ranges: < 2.6.1.1, >= 1055.v1346ba467ba1 and < 1074.1076.v39c30cecb_0e2, or >= 1105.vb_4e24a_c78b_81 and < 1112.vc87b_7a_3597f6
  2. Verify if credentials exist with custom name or description
    Navigate to Manage Jenkins > Manage Credentials and review any stored credentials. Check the 'Name' and 'Description' fields for any non-standard or user-supplied values.
    Affected if Credentials exist where the name or description field contains content that could have been injected by a user with Item/Configure permission
  3. Confirm presence of users with Item/Configure permission
    Navigate to Manage Jenkins > Manage Users or check Jenkins authorization matrix for users granted Item/Configure or Credentials/Create permissions
    Affected if Any user account or group has Item/Configure or Credentials/Create permissions, as this is required to exploit the vulnerability
  4. Inspect credential view pages for potential XSS
    Access the credential details pages (typically at /credentials/ or within job configurations) and view the page source or use browser developer tools to inspect whether name and description fields are properly HTML-encoded
    Affected if The name or description fields render as raw HTML/JavaScript without escaping (e.g., <script> tags appear literally in the page source)

If the Credentials Plugin version is in the affected ranges AND credentials with user-supplied name/description exist AND users with Item/Configure permission are present, the environment is vulnerable to stored XSS.

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 2.6.1.1 / 1074.1076.v39c30cecb_0e2 / 1112.vc87b_7a_3597f6 or later
Fixed in 2.6.1.11074.1076.v39c30cecb_0e21112.vc87b_7a_3597f6
Interim mitigation

Update Jenkins Credentials Plugin to version 1087.1089.v2f1b_9a_b_040e4, 1074.1076.v39c30cecb_0e2, 2.6.1.1, or any later patched version to remediate the XSS vulnerability.

Recommended fix High confidence

Upgrade to Jenkins Credentials Plugin 1087.1089.v2f1b_9a_b_040e4 or later

  1. Check current installed version of Jenkins Credentials plugin in Manage Jenkins > Manage Plugins > Installed
  2. If running a version < 2.6.1.1, or between 1055.v1346ba467ba1 and 1074.1076.v39c30cecb_0e2 (exclusive), or between 1105.vb_4e24a_c78b_81 and 1112.vc87b_7a_3597f6 (exclusive), the instance is vulnerable
  3. Navigate to Manage Jenkins > Manage Plugins > Available
  4. Locate Credentials plugin and select Update, or upload the new .hpi file from the Jenkins security advisory
  5. Restart Jenkins or wait for plugin to reload
  6. Verify the new version is 1087.1089.v2f1b_9a_b_040e4 or later
Caveat Review plugin changelog for compatibility with other plugins; minor point release upgrade unlikely to break functionality

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

Fix this in Credentials Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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