What is the severity of CVE-2020-2101?

CVE-2020-2101 is considered a medium severity vulnerability.

How do I fix CVE-2020-2101?

To fix CVE-2020-2101, upgrade Jenkins to version 2.219 or later, or to 2.204.2 if using LTS.

What impact does CVE-2020-2101 have on Jenkins?

CVE-2020-2101 can potentially allow attackers to perform timing attacks to reveal connection secrets.

Which versions of Jenkins are affected by CVE-2020-2101?

Jenkins versions 2.218 and earlier, as well as LTS versions 2.204.1 and earlier, are affected by CVE-2020-2101.

Is there a workaround for CVE-2020-2101?

There are no specific workarounds for CVE-2020-2101 other than upgrading to a secure version.

Vulnerability/
CVE-2020-2101

medium

5.3

CWE

203 208

29/1/2020

24/5/2022

4/8/2024

CVE-2020-2101

First published: Wed Jan 29 2020(Updated: )

Jenkins 2.218 and earlier, LTS 2.204.1 and earlier did not use a constant-time comparison function for validating connection secrets, which could potentially allow an attacker to use a timing attack to obtain this secret.

Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com

Affected Software	Affected Version	How to fix
Jenkins Jenkins	<=2.204.1
Jenkins Jenkins	<=2.218
maven/org.jenkins-ci.main:jenkins-core	>=2.205<=2.218	2.219
maven/org.jenkins-ci.main:jenkins-core	<=2.204.1	2.204.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-2101?
CVE-2020-2101 is considered a medium severity vulnerability.
How do I fix CVE-2020-2101?
To fix CVE-2020-2101, upgrade Jenkins to version 2.219 or later, or to 2.204.2 if using LTS.
What impact does CVE-2020-2101 have on Jenkins?
CVE-2020-2101 can potentially allow attackers to perform timing attacks to reveal connection secrets.
Which versions of Jenkins are affected by CVE-2020-2101?
Jenkins versions 2.218 and earlier, as well as LTS versions 2.204.1 and earlier, are affected by CVE-2020-2101.
Is there a workaround for CVE-2020-2101?
There are no specific workarounds for CVE-2020-2101 other than upgrading to a secure version.

collector/nvd-index
collector/nvd-api
collector/github-advisory-latest
alias/GHSA-w7jr-wqw6-54xc
alias/CVE-2020-2101
collector/nvd-cve
collector/github-advisory
agent/weakness
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/references
agent/severity
agent/description
agent/first-publish-date
agent/event
agent/trending
agent/tags
agent/source
vendor/jenkins
canonical/jenkins jenkins
version/jenkins jenkins/2.204.1
version/jenkins jenkins/2.218
package-manager/maven

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2020-2101?
CVE-2020-2101 is considered a medium severity vulnerability.
How do I fix CVE-2020-2101?
To fix CVE-2020-2101, upgrade Jenkins to version 2.219 or later, or to 2.204.2 if using LTS.
What impact does CVE-2020-2101 have on Jenkins?
CVE-2020-2101 can potentially allow attackers to perform timing attacks to reveal connection secrets.
Which versions of Jenkins are affected by CVE-2020-2101?
Jenkins versions 2.218 and earlier, as well as LTS versions 2.204.1 and earlier, are affected by CVE-2020-2101.
Is there a workaround for CVE-2020-2101?
There are no specific workarounds for CVE-2020-2101 other than upgrading to a secure version.