CVE-2015-5320
jenkins: Secret key not verified when connecting a slave (SECURITY-184)
Overview
Description
Jenkins before 1.638 and LTS before 1.625.2 do not properly verify the shared secret used in JNLP slave connections, which allows remote attackers to connect as slaves and obtain sensitive information or possibly gain administrative access by leveraging knowledge of the name of a slave.
Source: OX vulnerability database
Severity
6.8 · MEDIUM
CVSS 2.0 base score, scored by redhat.
- Access vector
- Network
- Access complexity
- Medium
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
Weakness: CWE-200
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Maven | org.jenkins-ci.main:jenkins-core | >=1.626, <1.638<1.625.2 | 1.6381.625.2 |
Open a package to see all its vulnerabilities.
Operating systems · 76 fixes
Red Hat 1 release · 76 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 7 | nodejs-pause-stream | 0:0.0.11-2.el7aos | RHSA-2016:0070 |
| 7 | nodejs-undefsafe | 0:0.0.3-1.el7aos | RHSA-2016:0070 |
| 7 | nodejs-ansi-wrap +1 | 0:0.1.0-1.el7aos | RHSA-2016:0070 |
| 7 | nodejs-map-stream +1 | 0:0.1.0-2.el7aos | RHSA-2016:0070 |
| 7 | nodejs-ansi-green +1 | 0:0.1.1-1.el7aos | RHSA-2016:0070 |
| 7 | nodejs-duplexer | 0:0.1.1-2.el7aos | RHSA-2016:0070 |
70 more rows
References
- rhn.redhat.com http://rhn.redhat.com/errata/RHSA-2016-0489.html
- access.redhat.com https://access.redhat.com/errata/RHSA-2016:0070
- access.redhat.com https://access.redhat.com/security/cve/CVE-2015-5320
- github.com https://github.com/jenkinsci/jenkins
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2015-5320
- wiki.jenkins-ci.org https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2015-5320
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.