CVE-2021-21615
jenkins: Filesystem traversal by privileged users
Overview
Description
Jenkins 2.275 and LTS 2.263.2 allows reading arbitrary files using the file browser for workspaces and archived artifacts due to a time-of-check to time-of-use (TOCTOU) race condition.
Source: OX vulnerability database
Severity
5.3 · MEDIUM
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Weakness: CWE-367
Affected packages · 2
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Bitnami | jenkins | <2.276.0 | 2.276.0 |
| Maven | org.jenkins-ci.main:jenkins-core | <2.263.3>=2.264, <2.276 | 2.263.32.276 |
Open a package to see all its vulnerabilities.
Operating systems · 12 fixes
Red Hat 2 releases · 7 packages
wont fix 1
fixed 11
jenkins
openshift-ansible
openshift-hyperkube
openshift-clients
conmon
runc
+1
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| 7 | jenkins | wont fix | — |
| 7 | jenkins | 0:2.263.3.1612434332-1.el7 | RHSA-2021:0429 |
| 7 | openshift-ansible +1 | 0:4.5.0-202102031005.p0.git.0.c6839a2.el7 | RHSA-2021:0429 |
| 7 | openshift-hyperkube | 0:4.5.0-202102050524.p0.git.0.9229406.el7 | RHSA-2021:0429 |
| 7 | openshift-clients +1 | 0:4.5.0-202102051529.p0.git.3612.61b096a.el7 | RHSA-2021:0429 |
| 7 | conmon | 2:2.0.21-1.rhaos4.5.el7 | RHSA-2021:0429 |
6 more rows
References
- www.openwall.com http://www.openwall.com/lists/oss-security/2021/01/26/2
- access.redhat.com https://access.redhat.com/security/cve/CVE-2021-21615
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2021-21615
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2021-21615
- www.jenkins.io https://www.jenkins.io/security/advisory/2021-01-26/#SECURITY-2197
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.