Skip to content
Fencer Vulns
medium 4.3

CVE-2021-21606 json

Arbitrary file existence check in file fingerprints in Jenkins

published 2021-01-13 5 y ago modified 2026-09-08 2 mo ago also BIT-jenkins-2021-21606 , EUVD-2022-3692 , GHSA-f585-9fw3-rj2m

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

Jenkins 2.274 and earlier, LTS 2.263.1 and earlier improperly validates the format of a provided fingerprint ID when checking for its existence allowing an attacker to check for the existence of XML files with a short path.

Patch / fix

  • maven org.jenkins-ci.main:jenkins-core 2.263.2, 2.275
  • bitnami jenkins 2.274.1
  • runc openshift 4.8 1.0.0-98.rhaos4.8.gitcd80260.el7
  • runc openshift 4.8 1.0.0-98.rhaos4.8.gitcd80260.el8
  • cri-o openshift 4.8 1.21.2-5.rhaos4.8.gitb27d974.el7
  • cri-o openshift 4.8 1.21.2-5.rhaos4.8.gitb27d974.el8
  • butane openshift 4.8 0.12.1-1.rhaos4.8.el8
  • ostree openshift 4.8 2020.7-5.el8_4
  • podman openshift 4.8 3.0.1-6.el8
  • haproxy openshift 4.8 2.2.13-1.el7

red hat advisories RHSA-2021:2437RHSA-2021:0637RHSA-2021:0429RHSA-2021:0423

  • jenkins Alpine 3.24, Alpine 3.23, Alpine 3.22 +10 more 2.275-r0

alpine advisories ALPINE-CVE-2021-21606

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • jenkins Arch Linux 2.275-1

arch linux advisories AVG-1446

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-21606 updated cvss 4.3

jenkins: Arbitrary file existence check in file fingerprints

  • Red Hat OpenShift Container Platform 3.11 jenkins 2.263.3.1612433584-1.el7
    fixed: vendor fix RHSA-2021:0637
  • Red Hat OpenShift Container Platform 4.5 conmon 2.0.21-1.rhaos4.5.el7, conmon 2.0.21-1.rhaos4.5.el8, jenkins 2.263.3.1612434332-1.el7, runc 1.0.0-72.rhaos4.5.giteadfc6b.el8, openshift 4.5.0-202102050524.p0.git.0.9229406.el7, openshift 4.5.0-202102050524.p0.git.0.9229406.el8, +9 more
    fixed: vendor fix RHSA-2021:0429
  • Red Hat OpenShift Container Platform 4.6 jenkins 2.263.3.1612434510-1.el8
    fixed: vendor fix RHSA-2021:0423
  • Red Hat OpenShift Container Platform 4.8 podman 3.0.1-6.el8, haproxy 2.2.13-1.el7, haproxy 2.2.13-1.el8, ostree 2020.7-5.el8_4, cri-tools 1.21.0-2.el7, cri-tools 1.21.0-2.el8, +134 more
    fixed: vendor fix RHSA-2021:2437
  • Red Hat Fuse 7 jenkins Red Hat OpenShift Container Platform 3.11 haproxy 1.8.28-1.el7, python-rsa 4.5-3.el7, python2-rsa 4.5-3.el7, haproxy18 1.8.28-1.el7, jenkins-2-plugins 3.11.1612862361-1.el7, prometheus 3.11.394-1.git.5026.2c9627f.el7, +39 more Red Hat OpenShift Container Platform 4.6 python-rsa 4.7-1.el8, python3-rsa 4.7-1.el8, runc 1.0.0-82.rhaos4.6.git086e841.el7, runc 1.0.0-82.rhaos4.6.git086e841.el8, cri-o 1.19.1-7.rhaos4.6.git6377f68.el7, jenkins-2-plugins 4.6.1612257979-1.el8, +16 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
OSV 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.main:jenkins-core
<2.263.2
>=2.264, <2.275
2.263.2
2.275
bitnami jenkins
<2.274.1
2.274.1

Affected products

  • Jenkins project Jenkins

Classification

Weakness
  • CWE-20 Improper Input Validation
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.