dbcve.org
Custom Checkbox ParameterApplication · Jenkins

CVE-2022-43425

MEDIUM · 5.4 CVSS v3.1 Published 2022-10-19
Fix available
A fix is available. Upgrade to after 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
Jenkins Custom Checkbox Parameter Plugin 1.4 and earlier does not escape the name and description of Custom Checkbox Parameter 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 Custom Checkbox Parameter Plugin versions 1.4 and earlier fails to properly escape/sanitize the name and description fields of Custom Checkbox Parameter parameters when rendering them on parameter display views. This allows attackers with Item/Configure permission to inject malicious JavaScript code into these fields, which executes when other users view the affected parameter pages (stored XSS).

MitigationUpdate to a patched version of the Custom Checkbox Parameter Plugin once available, or apply proper output encoding to the name and description fields in the plugin's view templates. Until patched, restrict Item/Configure permission to trusted users only.

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
Custom Checkbox ParameterApplication
Affected:<= 1.4

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 if Custom Checkbox Parameter Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the $JENKINS_HOME/plugins directory for the custom-checkbox-parameter plugin folder.
    Affected if The plugin is present in the installed plugins list or filesystem.
  2. Determine the installed plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab, locate Custom Checkbox Parameter, and note the Version column. Alternatively, examine the $JENKINS_HOME/plugins/custom-checkbox-parameter/META-INF/MANIFEST.MF file for the Plugin-Version attribute.
    Affected if The version is 1.4 or earlier.
  3. Identify jobs using Custom Checkbox Parameter
    Search job configurations for '<customCheckbox>' or 'custom-checkbox-parameter' references in config.xml files within $JENKINS_HOME/jobs/, or use the Jenkins script console with: Jenkins.instance.allItems.collect{ it.actions }.flatten().findAll{ it.class.name?.contains('CustomCheckboxParameter') }
    Affected if Any jobs or pipelines are configured with Custom Checkbox Parameter definitions.
  4. Inspect parameter configurations for unsanitized content
    Review the config.xml of affected jobs, or manually inspect the Configure page of jobs using Custom Checkbox Parameter. Look at the Name and Description fields for the parameter entries.
    Affected if The Name or Description fields contain HTML, JavaScript, or special characters that may be rendered unescaped.
  5. Verify Item/Configure permission assignments
    Review overall Matrix Authorization Strategy or Project-based Authorization at Manage Jenkins > Configure Global Security. Check which users or groups have the Overall/Administer or Item/Configure permission.
    Affected if There are users other than administrators granted Item/Configure permission on the affected system.

A user is affected if the Custom Checkbox Parameter Plugin version 1.4 or earlier is installed, there are jobs using this parameter type, and untrusted users have Item/Configure permission or can configure jobs containing these parameters.

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.4
Interim mitigation

Update to a patched version of the Custom Checkbox Parameter Plugin once available, or apply proper output encoding to the name and description fields in the plugin's view templates. Until patched, restrict Item/Configure permission to trusted users only.

Recommended fix Moderate confidence

Latest version newer than 1.4 (check Jenkins plugin repository for current release)

  1. 1. Navigate to Jenkins dashboard
  2. 2. Go to Manage Jenkins > Manage Plugins
  3. 3. Click on the 'Installed' tab
  4. 4. Locate 'Custom Checkbox Parameter' plugin in the list
  5. 5. If an update is available, click 'Update' or upgrade to the latest version
  6. 6. Restart Jenkins if required to apply the update
  7. 7. Verify the plugin has been updated to a version newer than 1.4

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

Fix this in Custom Checkbox Parameter Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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