dbcve.org
Custom Build PropertiesApplication · Jenkins

CVE-2022-46686

MEDIUM · 5.4 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to after 2.79.vc095ccc85094 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 Build Properties Plugin 2.79.vc095ccc85094 and earlier does not escape property values and build display names on the Custom Build Properties and Build Summary pages, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to set or change these values.

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 Build Properties Plugin versions 2.79.vc095ccc85094 and earlier fails to properly escape HTML/script characters in property values and build display names displayed on the Custom Build Properties and Build Summary pages. This allows attackers with the ability to set or modify these values to inject malicious JavaScript that executes in the browsers of other users who view these pages, resulting in a stored cross-site scripting (XSS) vulnerability.

MitigationUpdate the Custom Build Properties Plugin to a version newer than 2.79.vc095ccc85094, which includes proper output encoding. Review existing build properties for any maliciously injected scripts.

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 Build PropertiesApplication
Affected:<= 2.79.vc095ccc85094

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 Custom Build Properties plugin is installed
    Go to Jenkins Manage Jenkins > Manage Plugins > Installed tab and search for 'Custom Build Properties' or check the plugin manifest file in JENKINS_HOME/plugins/
    Affected if The plugin is installed and its version is 2.79.vc095ccc85094 or earlier
  2. Check the installed plugin version
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, find Custom Build Properties Plugin, and note the version column. Alternatively, inspect the plugin's .hpi file for the version manifest.
    Affected if Version listed is 2.79.vc095ccc85094 or any version number lower than it
  3. Identify builds using Custom Build Properties
    Navigate to build history pages for jobs that use the Custom Build Properties plugin. Look for builds that have custom property values or custom build display names set.
    Affected if Builds exist with custom properties or display names defined
  4. Inspect property values for suspicious content
    View the Custom Build Properties page for recent builds (build > Custom Build Properties link) and examine the property name/value pairs. Look for HTML tags, script tags, javascript: URIs, or unusual encoded characters.
    Affected if Any property values contain HTML, script tags, or JavaScript code that could execute in a browser
  5. Check Build Summary pages for injected content
    View the Build Summary section on build result pages where the Custom Build Properties plugin displays information. Inspect the rendered HTML for unsanitized script tags or event handlers.
    Affected if The Build Summary displays property values or display names containing unescaped HTML/script content

A user is affected if the Custom Build Properties plugin version is 2.79.vc095ccc85094 or earlier AND builds exist that have custom property values or display names visible on the Custom Build Properties or Build Summary pages.

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 2.79.vc095ccc85094
Interim mitigation

Update the Custom Build Properties Plugin to a version newer than 2.79.vc095ccc85094, which includes proper output encoding. Review existing build properties for any maliciously injected scripts.

Recommended fix Moderate confidence

Custom Build Properties Plugin version higher than 2.79.vc095ccc85094 (check Jenkins Security Advisory 2022-12-07 for exact fixed version)

  1. Log in to Jenkins as an administrator
  2. Navigate to 'Manage Jenkins'
  3. Click on 'Manage Plugins'
  4. Select the 'Updates' tab
  5. Locate 'Custom Build Properties' plugin in the list
  6. If an update is available, select the plugin and click 'Download now and install after restart'
  7. Wait for the plugin to download and install
  8. Restart Jenkins to complete the installation

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

Fix this in Custom Build Properties 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-46686 — 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-46686 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