Exposure of Sensitive Information in Jenkins Core
Research is free — Hunters explains how the bug works, the root-cause code pattern, how the fix addresses it, and how to test whether a target is affected, in chat. Investigate & write exploit is a paid run — the engine reads the advisory and fix commits, then builds and validates a working proof-of-concept exploit with reproduction steps.
Affected versions
0 → fixed in 2.3
Details
Jenkins before 2.3 and LTS before 1.651.2 allow remote authenticated users with read access to obtain sensitive plugin installation information by leveraging missing permissions checks in unspecified XML/JSON API endpoints.
The fix
No fix commit could be resolved for this advisory (it may reference an issue tracker or a non-GitHub patch). See the references below.
References
- ADVISORYhttps://nvd.nist.gov/vuln/detail/CVE-2016-3723
- WEBhttps://access.redhat.com/errata/RHSA-2016:1206
- WEBhttps://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11
- WEBhttps://www.cloudbees.com/jenkins-security-advisory-2016-05-11
- WEBhttp://rhn.redhat.com/errata/RHSA-2016-1773.html