dbcve.org
Owasp Dependency CheckApplication · Jenkins

CVE-2017-1000109

MEDIUM · 6.1 CVSS v3.0 Published 2017-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 custom Details view of the Static Analysis Utilities based OWASP Dependency-Check Plugin, was vulnerable to a persisted cross-site scripting vulnerability: Malicious users able to influence the input to this 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

The OWASP Dependency-Check Plugin for Jenkins contains a stored XSS vulnerability in its custom Details view. Malicious users who can influence the plugin's input can inject arbitrary HTML/JavaScript that persists and executes when other users view the affected Details page.

MitigationUpdate the OWASP Dependency-Check Plugin to a patched version. Until an update is available, restrict access to trusted users only and consider disabling the affected plugin.

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
Owasp Dependency CheckApplication
Affected:= 1.0.1= 1.0.1.1= 1.0.2= 1.0.3= 1.0.4= 1.0.4.1= 1.0.5= 1.0.7= 1.0.8= 1.1.0= 1.1.1= 1.1.1.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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/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 OWASP Dependency-Check Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and look for 'OWASP Dependency-Check' in the list of installed plugins, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i 'dependency-check'
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, find the OWASP Dependency-Check plugin, and note the version number displayed in the 'Version' column
    Affected if The installed version matches one of these: 1.0.1, 1.0.1.1, 1.0.2, 1.0.3, 1.0.4, 1.0.4.1, 1.0.5, 1.0.7, 1.0.8, 1.1.0, 1.1.1, 1.1.1.1
  3. Confirm the Details view feature is in use
    Look for any Jenkins jobs that have the OWASP Dependency-Check post-build action enabled, or check if any build artifacts include dependency-check reports that are accessible via the Jenkins web interface
    Affected if The plugin's post-build action is configured on any job and reports are accessible through the Jenkins UI
  4. Check for untrusted or anonymous user access
    Review Jenkins user permissions via Manage Jenkins > Manage Users and check global security settings and job-level permissions to determine if users with limited trust can access the plugin's output pages
    Affected if Users other than administrators can access the dependency-check results or Details view pages

The environment is affected if the OWASP Dependency-Check Plugin is installed at a version matching 1.0.1 through 1.1.1.1, the plugin is actively used in jobs, and untrusted users can access the Details view where the XSS payload would execute.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the OWASP Dependency-Check Plugin to a patched version. Until an update is available, restrict access to trusted users only and consider disabling the affected plugin.

Fix this in Owasp Dependency Check 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 help mitigating

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-1000109 — 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-1000109 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