Описание
Observable Discrepancy and Observable Timing Discrepancy in Jenkins Configuration as Code Plugin
Jenkins Configuration as Code Plugin prior to 1.55.1, 1.54.1, 1.53.1, and 1.47.1 does not use a constant-time comparison when checking whether two authentication tokens are equal.
This could potentially allow attackers to use statistical methods to obtain a valid authentication token.
Configuration as Code Plugin 1.55.1, 1.54.1, 1.53.1, and 1.47.1 now uses a constant-time comparison when validating authentication tokens.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2022-23106
- https://github.com/jenkinsci/configuration-as-code-plugin/commit/4f425675edf77d382a6fd10890f1a704ff3b2277
- https://github.com/CVEProject/cvelist/blob/00bfb5abeecc9f553a2f42954ee540e493498ee9/2022/23xxx/CVE-2022-23106.json
- https://www.jenkins.io/security/advisory/2022-01-12/#SECURITY-2141
- http://www.openwall.com/lists/oss-security/2022/01/12/6
Пакеты
io.jenkins:configuration-as-code
= 1.55
1.55.1
io.jenkins:configuration-as-code
= 1.54
1.54.1
io.jenkins:configuration-as-code
>= 1.48, < 1.53.1
1.53.1
io.jenkins:configuration-as-code
< 1.47.1
1.47.1
Связанные уязвимости
Jenkins Configuration as Code Plugin 1.55 and earlier used a non-constant time comparison function when validating an authentication token allowing attackers to use statistical methods to obtain a valid authentication token.
Jenkins Configuration as Code Plugin 1.55 and earlier used a non-constant time comparison function when validating an authentication token allowing attackers to use statistical methods to obtain a valid authentication token.