CVE-2017-1000109: Persistent XSS vulnerability in Jenkins OWASP Dependency-Check Plugin
Summary
CVE-2017-1000109: Persistent XSS vulnerability in Jenkins OWASP Dependency-Check Plugin. Affects org.jenkins-ci.plugins:dependency-check-jenkins-plugin versions < 2.0.1.2. Fixed in 2.0.1.2. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Jenkins OWASP Dependency-Check Plugin is a Static Analysis Utilities based plugin that helps identify vulnerabilities in project dependencies. It scans the project's dependencies and provides a detailed report on any known vulnerabilities. The plugin is widely used in Jenkins CI/CD pipelines to ensure the security of software projects.
Vulnerability Detail
The plugin's custom Details view was found to have a persistent cross-site scripting (XSS) vulnerability. This means that malicious users with the ability to manipulate the input to the plugin could inject arbitrary HTML code into the Details view. This vulnerability could allow an attacker to execute malicious scripts in the context of other users who view the affected Details view. The vulnerability has a CVSS score of 6.1, indicating a moderate severity level.
How To Fix
Latest published version: 5.6.5 as of 22 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2.0.1.2
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. However, it is crucial to ensure that the plugin is updated to the fixed version as soon as possible to mitigate the risk of exploitation.
Conclusion
The Jenkins OWASP Dependency-Check Plugin was found to have a persistent XSS vulnerability in its custom Details view. This vulnerability allows attackers to inject arbitrary HTML code, potentially leading to the execution of malicious scripts. To mitigate this risk, it is crucial to upgrade the plugin to version 2.0.1.2 or later. For further assistance or support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.plugins:dependency-check-jenkins-plugin →
FAQ
The vulnerability allows an attacker to inject arbitrary HTML code into the Details view of the Jenkins OWASP Dependency-Check Plugin. This can lead to the execution of malicious scripts in the context of other users who view the affected view.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your Jenkins instance is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, and you can check the impact of this vulnerability without any signup or installation.
There are no known public exploits available for this vulnerability at the time of writing. However, it is essential to patch the vulnerability as soon as possible to prevent potential exploitation.
Yes, this vulnerability can be exploited remotely. An attacker with the ability to manipulate the input to the plugin can inject malicious HTML code, which can then be executed when other users view the affected Details view.
You can find more information about this vulnerability, including the affected versions and fix details, in the GitHub Advisory Database (https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/05/GHSA-65cq-whr4-7c2v/GHSA-65cq-whr4-7c2v.json).
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.plugins:dependency-check-jenkins-plugin.
