Jenkins improperly ensures trust separation
Jenkins prior to 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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2014-3665US | medium6.8 | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHBA-2014:1630WEB
- https://access.redhat.com/security/cve/CVE-2014-3665WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=1147767WEB
- https://nvd.nist.gov/vuln/detail/CVE-2014-3665ADVISORY
- https://wiki.jenkins-ci.org/display/JENKINS/Slave+To+Master+Access+ControlWEB
- https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2014-10-30WEB
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