dbcve.org
Mask PasswordsApplication · Jenkins

CVE-2022-29043

MEDIUM · 5.4 CVSS v3.1 Published 2022-04-12
Fix available
A fix is available. Upgrade to after 3.0 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 Mask Passwords Plugin 3.0 and earlier does not escape the name and description of Non-Stored Password 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

The Jenkins Mask Passwords Plugin versions 3.0 and earlier fails to properly escape the name and description fields of Non-Stored Password parameters when rendering them in parameter display views. This allows an authenticated attacker with Item/Configure permission to inject malicious JavaScript code that executes in the browsers of other users viewing those parameters, resulting in a stored cross-site scripting (XSS) vulnerability.

MitigationUpgrade the Mask Passwords Plugin to a patched version that implements proper output escaping for parameter names and descriptions, or restrict Item/Configure permission 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
Mask PasswordsApplication
Affected:<= 3.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. Verify Mask Passwords Plugin installation and version
    Navigate to Manage Jenkins > Manage Plugins > Installed, or use the Jenkins CLI: /pluginManager/plugin/{mask-passwords}/api/json?pretty=true to check the installed version
    Affected if The Mask Passwords Plugin is installed and its version is 3.0 or earlier
  2. Identify Non-Stored Password parameters in use
    Review Jenkins jobs that use the Mask Passwords plugin and specifically look for 'Non-Stored Password' parameter types in the job configuration under Build Parameters
    Affected if Jobs contain Non-Stored Password parameters configured with custom names or descriptions that could contain injected scripts
  3. Inspect parameter names and descriptions for unescaped content
    View the parameter display pages of configured jobs (go to a job > Parameters tab) and examine the rendered HTML source for Non-Stored Password parameters, looking for unsanitized content in name/description fields
    Affected if The rendered parameter names or descriptions contain raw HTML/JavaScript that is not properly escaped (visible as literal script tags or unescaped quotes in page source)

You are affected if the Mask Passwords Plugin version 3.0 or earlier is installed AND jobs contain Non-Stored Password parameters with user-controlled names or descriptions that render unescaped HTML content.

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

Upgrade the Mask Passwords Plugin to a patched version that implements proper output escaping for parameter names and descriptions, or restrict Item/Configure permission to trusted users only until a patch is available.

Recommended fix Moderate confidence

Mask Passwords plugin version 3.1 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. Search for 'Mask Passwords' plugin
  5. 5. If an update is available, click 'Update now'
  6. 6. Restart Jenkins to complete the upgrade
  7. 7. Alternatively, manually download the fixed plugin version (3.1 or later) from the Jenkins plugin repository and upload it via 'Advanced' > 'Upload Plugin'

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

Fix this in Mask Passwords Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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