First published: Wed Jan 12 2022(Updated: )
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.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins Configuration As Code | <=1.55 | |
maven/io.jenkins:configuration-as-code | <1.47.1 | 1.47.1 |
maven/io.jenkins:configuration-as-code | >=1.48<1.53.1 | 1.53.1 |
maven/io.jenkins:configuration-as-code | =1.54 | 1.54.1 |
maven/io.jenkins:configuration-as-code | =1.55 | 1.55.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-23106 is classified as a high severity vulnerability due to its potential to compromise authentication tokens.
To mitigate CVE-2022-23106, upgrade the Jenkins Configuration as Code Plugin to versions 1.55.1, 1.54.1, 1.53.1, or later.
Versions 1.55 and earlier of the Jenkins Configuration as Code Plugin are affected by CVE-2022-23106.
CVE-2022-23106 is an authentication vulnerability allowing attackers to exploit non-constant time comparison functions.
Yes, attackers can apply statistical methods to obtain a valid authentication token due to the vulnerability in CVE-2022-23106.