Exposure of Sensitive Information to an Unauthorized Actor in Jenkins
Jenkins before versions 2.44 and 2.32.2 is vulnerable to an information exposure in the internal API that allows access to item names that should not be visible (SECURITY-380). This only affects anonymous users (other users legitimately have access) that were able to get a list of items via an UnprotectedRootAction.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2017-2606US | medium4.3 | — | ||
Jenkins before versions 2.44, 2.32.2 is vulnerable to an information exposure in the internal API that allows access to item names that should not be visible (SECURITY-380). This o… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.securityfocus.com/bid/95962WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2606WEB
- https://github.com/jenkinsci/jenkinsPACKAGE
- https://github.com/jenkinsci/jenkins/commit/09cfbc9cd5c9df7c763bc976b7f5c51266b63719WEB
- https://jenkins.io/security/advisory/2017-02-01WEB
- https://nvd.nist.gov/vuln/detail/CVE-2017-2606ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan