Jenkins before 1.587 and LTS before 1.580.1 do not properly ensure trust separation between a master and slaves, which might allow remote attackers to execute arbitrary code on the master by leveraging access to the slave.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Jenkins | Jenkins | * | 1.586 (including) |
| Red Hat OpenShift Enterprise 2.1 | RedHat | jenkins-0:1.565.3-1.el6op | * |
| Red Hat OpenShift Enterprise 2.1 | RedHat | jenkins-plugin-openshift-0:0.6.40.1-0.el6op | * |
| Red Hat OpenShift Enterprise 2.1 | RedHat | openshift-origin-cartridge-jenkins-0:1.20.3.5-1.el6op | * |
| Jenkins | Ubuntu | precise | * |
References
- https://bugzilla.redhat.com/show_bug.cgi?id=1147767
- https://wiki.jenkins-ci.org/display/JENKINS/Slave+To+Master+Access+Control
- https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2014-10-30
- https://www.cloudbees.com/jenkins-security-advisory-2014-10-30
- https://bugzilla.redhat.com/show_bug.cgi?id=1147767
- https://wiki.jenkins-ci.org/display/JENKINS/Slave+To+Master+Access+Control
- https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2014-10-30
- https://www.cloudbees.com/jenkins-security-advisory-2014-10-30