First published: Wed Mar 25 2015(Updated: )
This vulnerability allows attackers to create malicious XML documents and feed that into Jenkins, which causes 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-1811 is considered a high severity vulnerability due to its ability to expose sensitive information.
To fix CVE-2015-1811, upgrade Jenkins to a version above 1.600 or 1.596.1 depending on the specific build you are using.
CVE-2015-1811 allows attackers to exploit Jenkins by processing malicious XML, potentially leading to unauthorized data exposure.
CVE-2015-1811 affects Jenkins versions below 1.596.1 and 1.600.
There is no specific workaround for CVE-2015-1811; updating to a patched version is the recommended action.