CVE-2016-3727
jenkins: Granting the permission to read node configurations allows access to overall system configuration (SECURITY-281)
Overview
Description
The API URL computer/(master)/api/xml in Jenkins before 2.3 and LTS before 1.651.2 allows remote authenticated users with extended read permission for the master node to obtain sensitive information about the global configuration via unspecified vectors.
Source: OX vulnerability database
Severity
4.3 · MEDIUM
CVSS 3.0 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Weakness: CWE-200
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Maven | org.jenkins-ci.main:jenkins-core | >=1.652, <2.3<1.651.2 | 2.31.651.2 |
Open a package to see all its vulnerabilities.
Operating systems · 2 fixes
Red Hat 1 release · 2 packages
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 7 | jenkins-plugin-openshift-pipeline | 0:1.0.12-1.el7 | RHSA-2016:1206 |
| 7 | jenkins | 0:1.651.2-1.el7 | RHSA-2016:1206 |
References
- rhn.redhat.com http://rhn.redhat.com/errata/RHSA-2016-1773.html
- access.redhat.com https://access.redhat.com/errata/RHSA-2016:1206
- access.redhat.com https://access.redhat.com/security/cve/CVE-2016-3727
- github.com https://github.com/jenkinsci/jenkins
- github.com https://github.com/jenkinsci/jenkins/commit/d66ad6f3ee46a5c6bb865bb831e8cdfc74cd7eb3
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2016-3727
- wiki.jenkins-ci.org https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11
- www.cloudbees.com https://www.cloudbees.com/jenkins-security-advisory-2016-05-11
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2016-3727
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.