Non-constant time comparison of inbound TCP agent connection secret
Jenkins 2.218 and earlier, LTS 2.204.1 and earlier does not use a constant-time comparison validating the connection secret when an inbound TCP agent connection is initiated. This could potentially allow attackers to use statistical methods to obtain the connection secret. Jenkins 2.219, LTS 2.204.2 now uses a constant-time comparison function for verifying connection secrets.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-2101US | medium5.3 | — | ||
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 u… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2020/01/29/1WEB
- https://access.redhat.com/errata/RHBA-2020:0402WEB
- https://access.redhat.com/errata/RHBA-2020:0675WEB
- https://access.redhat.com/errata/RHSA-2020:0681WEB
- https://access.redhat.com/errata/RHSA-2020:0683WEB
- https://github.com/jenkinsci/jenkinsPACKAGE
- https://github.com/jenkinsci/jenkins/commit/0ba36508187ff771bba87feaf03057496775064cWEB
- https://jenkins.io/security/advisory/2020-01-29/#SECURITY-1659WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan