dbcve.org
Spring ConfigFramework / library · Jenkins

CVE-2022-46687

MEDIUM · 5.4 CVSS v3.1 Published 2022-12-12
Fix available
A fix is available. Upgrade to 2.0.1 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 Spring Config Plugin 2.0.0 and earlier does not escape build display names shown on the Spring Config view, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to change build display names.

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 Spring Config Plugin 2.0.0 and earlier fails to escape build display names when rendering them in the Spring Config view, allowing stored XSS injection. Attackers with the ability to modify build display names can inject malicious scripts that execute when other users view the Spring Config page.

MitigationUpgrade to a patched version of the Spring Config Plugin that properly escapes build display names. If no patched version exists, manually escape output in the affected view using appropriate HTML encoding functions before rendering user-controlled display names.

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
Spring ConfigFramework / library
Affected:< 2.0.1

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 Spring Config Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed, or check for the spring-config plugin directory in $JENKINS_HOME/plugins/
    Affected if The Spring Config Plugin appears in the list of installed plugins
  2. Determine installed plugin version
    In Jenkins plugin manager, find the Spring Config Plugin and note the version number displayed, or inspect the plugin's MANIFEST.MF file
    Affected if The version is 2.0.0 or earlier (any version prior to 2.0.1)
  3. Identify if build display names are used with Spring Config
    Review your Jenkins jobs that use the Spring Config Plugin and check if any builds have custom display names set via the build display name feature
    Affected if Any builds in jobs using Spring Config have custom display names configured
  4. Inspect rendered Spring Config view for XSS vulnerability
    Access the Spring Config view for a build with a custom display name (typically at /job/JOB_NAME/BUILD_NUMBER/spring-config/) and view the page source to see if build display names are HTML-encoded or rendered raw
    Affected if Display names are rendered without HTML encoding (raw output visible in source)

A user is affected if the Spring Config Plugin version is 2.0.0 or earlier AND builds with custom display names exist in jobs using the Spring Config plugin, with the display names rendered unencoded in the Spring Config view.

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.0.1 or later
Fixed in 2.0.1
Interim mitigation

Upgrade to a patched version of the Spring Config Plugin that properly escapes build display names. If no patched version exists, manually escape output in the affected view using appropriate HTML encoding functions before rendering user-controlled display names.

Recommended fix High confidence

2.0.1

  1. Navigate to Jenkins dashboard
  2. Go to 'Manage Jenkins'
  3. Click on 'Manage Plugins'
  4. Select the 'Installed' tab
  5. Locate 'Spring Config' plugin in the list
  6. If an update is available, check the plugin and click 'Update'
  7. Alternatively, if upgrading manually, download Spring Config Plugin version 2.0.1 or later from the Jenkins plugin repository
  8. Restart Jenkins to apply the update

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

Fix this in Spring Config Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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