Sidebar LinkApplication · Jenkins

CVE-2017-1000088

MEDIUM · 5.4 CVSS v3.0 Published 2017-10-05
Fix available
A fix is available. Upgrade to after 1.8 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 Sidebar Link plugin allows users able to configure jobs, views, and agents to add entries to the sidebar of these objects. There was no input validation, which meant users were able to use javascript: schemes for these links.

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 Sidebar Link plugin for Jenkins allowed users with job/view/agent configuration permissions to inject JavaScript code via javascript: URLs in sidebar links due to missing input validation. This stored XSS vulnerability allowed malicious links to execute in the browsers of other users viewing the affected sidebar entries.

MitigationUpgrade to a patched version of the Sidebar Link plugin that implements URL scheme validation (rejecting javascript: and other dangerous schemes), or restrict configuration permissions until the patch can be applied.

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
Sidebar LinkApplication
Affected:<= 1.8

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 Sidebar Link plugin is installed
    Go to Manage Jenkins > Manage Plugins > Installed tab and look for 'Sidebar Link' in the list, or check the $JENKINS_HOME/plugins directory for the sidebar-link plugin folder
    Affected if The plugin is present in the plugin list or file system
  2. Check the installed version of Sidebar Link plugin
    In Manage Jenkins > Manage Plugins > Installed, find the Sidebar Link plugin and read the Version column; compare against the affected range (versions <= 1.8)
    Affected if The installed version number is 1.8 or lower
  3. Identify configured sidebar links in jobs
    Review job configurations: for each job, go to Configure > Sidebar Links section and inspect any defined links for their URL values
    Affected if Any sidebar link URL contains 'javascript:' or other potentially dangerous URL schemes (e.g., data:, vbscript:)
  4. Identify configured sidebar links in views and agents
    Review view configurations (Manage Jenkins > Manage Views > configure) and agent configurations (manage each agent) for any sidebar links with unvalidated URL fields
    Affected if Any view or agent sidebar link URLs contain 'javascript:' or similar dangerous schemes
  5. Check which users have permission to configure sidebar links
    Review Jenkins authorization matrix or role-based access control settings to determine which users or groups have Job/View/Agent Configure permissions
    Affected if Users with elevated or broad configuration permissions exist and the plugin is installed and vulnerable

You are affected if the Sidebar Link plugin is installed at version 1.8 or lower AND any sidebar links containing javascript: or other dangerous URL schemes are present in jobs, views, or agent configurations.

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

Upgrade to a patched version of the Sidebar Link plugin that implements URL scheme validation (rejecting javascript: and other dangerous schemes), or restrict configuration permissions until the patch can be applied.

Fix this in Sidebar Link 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-2017-1000088 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-1000088 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