First published: Wed Mar 25 2015(Updated: )
This vulnerability allows users with the read access to Jenkins to retrieve arbitrary XML document on the server, resulting in the exposure of sensitive information inside/outside Jenkins. External References: <a href="https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-02-27">https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-02-27</a>
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins Cloudbees | <1.596.1 | |
Jenkins Cloudbees | <1.600 | |
maven/org.jenkins-ci.main:jenkins-core | <1.596.1 | 1.596.1 |
maven/org.jenkins-ci.main:jenkins-core | >=1.597<1.600 | 1.600 |
<1.596.1 | ||
<1.600 | ||
redhat/Jenkins | <1.600 | 1.600 |
redhat/Jenkins | <1.596.1 | 1.596.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-1809 is classified as a medium severity vulnerability.
To fix CVE-2015-1809, upgrade Jenkins to version 1.596.1 or 1.600, or later.
CVE-2015-1809 affects Jenkins installations prior to version 1.596.1 and 1.600.
CVE-2015-1809 may expose sensitive information contained in arbitrary XML documents on the server.
Yes, users with read access in Jenkins can exploit CVE-2015-1809 to access sensitive information.