CVE-2017-1000388
Description
Jenkins Dependency Graph Viewer plugin 0.12 and earlier lacks permission checks on an API endpoint, allowing users with Overall/Read permission to modify the dependency graph.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Jenkins Dependency Graph Viewer plugin 0.12 and earlier lacks permission checks on an API endpoint, allowing users with Overall/Read permission to modify the dependency graph.
Vulnerability
The Jenkins Dependency Graph Viewer plugin version 0.12 and earlier does not perform permission checks for the API endpoint that modifies the dependency graph. This allows any user with Overall/Read permission to modify the data. [1][2]
Exploitation
An attacker needs Overall/Read permission on the Jenkins instance, which is typically granted to authenticated users. They can then send a request to the vulnerable API endpoint to modify the dependency graph without needing additional permissions. [2]
Impact
Successful exploitation allows an attacker to modify the dependency graph data, potentially disrupting project dependencies or misrepresenting relationships. The impact is considered low as it only affects the graph data and does not lead to code execution or data leakage. [1][2]
Mitigation
The vulnerability was fixed in version 0.13 of the Jenkins Dependency Graph Viewer plugin, released after the security advisory on 2017-10-23. Users should update to version 0.13 or later. [2]
AI Insight generated on May 22, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
org.jenkins-ci.plugins:depgraph-viewMaven | < 0.13 | 0.13 |
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
4- github.com/advisories/GHSA-vhh3-mvc4-hhq6ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2017-1000388ghsaADVISORY
- jenkins.io/security/advisory/2017-10-23ghsaWEB
- jenkins.io/security/advisory/2017-10-23/mitrex_refsource_CONFIRM
News mentions
0No linked articles in our index yet.