dbcve.org
Static Analysis UtilitiesApplication · Jenkins

CVE-2017-1000102

MEDIUM · 5.4 CVSS v3.0 Published 2017-10-05
Fix available
A fix is available. Upgrade to after 1.91 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
The Details view of some Static Analysis Utilities based plugins, was vulnerable to a persisted cross-site scripting vulnerability: Malicious users able to influence the input to these plugins, for example the console output which is parsed to extract build warnings (Warnings Plugin), could insert arbitrary HTML into this view.

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

This is a persisted cross-site scripting (XSS) vulnerability in Jenkins plugins based on Static Analysis Utilities. The Details view fails to properly sanitize input from sources like console output (used to extract build warnings), allowing authenticated users with the ability to influence plugin input to inject arbitrary HTML/JavaScript that persists in the Details view.

MitigationUpdate affected Static Analysis Utilities-based plugins to versions that include proper input sanitization, or implement output encoding for the Details view to prevent HTML injection from untrusted input sources.

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
Static Analysis UtilitiesApplication
Affected:<= 1.91

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.0/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 Static Analysis Utilities plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i 'static-analysis'
    Affected if The Static Analysis Utilities plugin appears in the installed plugins list
  2. Check the installed version of Static Analysis Utilities
    In the plugin manager, click on the Static Analysis Utilities plugin and note the version shown, or check the plugin's manifest file (META-INF/MANIFEST.MF) in the plugin's .jpi file
    Affected if The version number is 1.91 or lower
  3. Identify plugins based on Static Analysis Utilities
    Review installed plugins for known analysis plugins that depend on Static Analysis Utilities (e.g., Checkstyle, PMD, FindBugs, and similar code analysis plugins)
    Affected if Any analysis plugins derived from Static Analysis Utilities are installed alongside the vulnerable utility plugin
  4. Verify access to the Details view of analysis results
    Navigate to a completed build that has analysis results, then access the analysis plugin's Details view (typically via the build page > Static Analysis Utilities-based plugin link)
    Affected if The Details view is accessible and displays extracted information from build artifacts or console output
  5. Confirm console output or build artifact processing is in use
    Review job configurations to see if any jobs are configured to parse console output or build artifacts using the analysis plugins
    Affected if Build jobs feed console output or build warnings to the analysis plugins that use the Static Analysis Utilities framework

A user is affected if Static Analysis Utilities plugin version 1.91 or lower is installed AND analysis plugins based on it are in use, allowing injection of unsanitized input that renders in the Details 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.

From vendor data
Upgrade available Upgrade to a release after 1.91
Interim mitigation

Update affected Static Analysis Utilities-based plugins to versions that include proper input sanitization, or implement output encoding for the Details view to prevent HTML injection from untrusted input sources.

Fix this in Static Analysis Utilities Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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