Skip to content
Fencer Vulns
high 8.6

CVE-2020-2099 json

Inbound TCP Agent Protocol/3 authentication bypass in Jenkins

published 2020-01-29 6 y ago modified 2026-09-08 2 mo ago also BIT-jenkins-2020-2099 , EUVD-2022-5008 , GHSA-qp4f-2w67-c8hw

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

Summary

Jenkins 2.213 and earlier, LTS 2.204.1 and earlier improperly reuses encryption key parameters in the Inbound TCP Agent Protocol/3, allowing unauthorized attackers with knowledge of agent names to obtain the connection secrets for those agents, which can be used to connect to Jenkins, impersonating those agents.

Patch / fix

  • maven org.jenkins-ci.main:jenkins-core 2.204.2, 2.214
  • bitnami jenkins 2.218.1
  • jenkins openshift 4.3 2.204.2.1583446818-1.el7
  • cri-o openshift 3.11 1.11.16-0.5.dev.rhaos3.11.git3f89eba.el7
  • jenkins openshift 3.11 2.204.2.1580891656-1.el7
  • prometheus openshift 3.11 3.11.170-1.git.1.227bc98.el7
  • openshift-kuryr openshift 3.11 3.11.170-1.git.1.7265da1.el7
  • atomic-openshift openshift 3.11 3.11.170-1.git.0.00cac56.el7
  • jenkins-2-plugins openshift 3.11 3.11.1579107288-1.el7
  • openshift-ansible openshift 3.11 3.11.170-2.git.5.8802564.el7

red hat advisories RHBA-2020:0675RHBA-2020:0402

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-2020-2099 updated cvss 8.6

jenkins: Inbound TCP Agent Protocol/3 authentication bypass

  • Red Hat OpenShift Container Platform 3.11 jenkins 2.204.2.1580891656-1.el7, jenkins-2-plugins 3.11.1579107288-1.el7, prometheus 3.11.170-1.git.1.227bc98.el7, openshift-kuryr 3.11.170-1.git.1.7265da1.el7, atomic-openshift 3.11.170-1.git.0.00cac56.el7, cri-o 1.11.16-0.5.dev.rhaos3.11.git3f89eba.el7, +37 more
    fixed: vendor fix RHBA-2020:0402
  • Red Hat OpenShift Container Platform 4.3 jenkins 2.204.2.1583446818-1.el7
    fixed: vendor fix RHBA-2020:0675
  • Red Hat OpenShift Container Platform 4.4 openshift4/ose-cli v4.4.0-202004261927, openshift4/ose-pod v4.4.0-202004261927, openshift4/ose-etcd v4.4.0-202004261927, openshift4/ose-tests v4.4.0-202004261927, openshift4/ose-console v4.4.0-202004261927, openshift4/ose-coredns v4.4.0-202004261927, +76 more
    fixed: vendor fix RHBA-2020:0581
  • Red Hat OpenShift Container Platform 4.5 openshift4/ose-cli v4.5.0-202007012112.p0, openshift4/ose-pod v4.5.0-202007012112.p0, openshift4/ose-etcd v4.5.0-202007012112.p0, openshift4/ose-tests v4.5.0-202007100518.p0, openshift4/ose-coredns v4.5.0-202007012112.p0, openshift4/ose-grafana v4.5.0-202007012112.p0, +71 more
    fixed: vendor fix RHBA-2020:2409
  • Red Hat OpenShift Container Platform 4.3 buildah 1.11.6-4.el8, cri-tools 1.17.0-1.el7, cri-tools 1.17.0-2.el8, ovn2.12 2.12.0-32.el7fdn, skopeo 0.1.40-4.rhaos.el8, buildah-tests 1.11.6-4.el8, +27 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.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.main:jenkins-core
<2.204.2
>=2.205, <2.214
2.204.2
2.214
bitnami jenkins
<2.218.1
2.218.1

Affected products

  • Jenkins project Jenkins

Classification

Weakness
  • CWE-323 Reusing a Nonce, Key Pair in Encryption
  • CWE-330 Use of Insufficiently Random Values
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.