Observable Discrepancy and Observable Timing Discrepancy in Jenkins Configuration as Code Plugin
Jenkins project Jenkins Configuration as Code Plugin
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.jenkins:configuration-as-code Maven |
|
|
Jenkins project Jenkins Configuration as Code Plugin
| Product | Affected | Fixed in |
|---|---|---|
| io.jenkins:configuration-as-code Maven |
|
|
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.
From the CVE record · jenkins
Jenkins Configuration as Code Plugin uses a non-constant-time comparison when validating an authentication token. An attacker can use statistical methods to obtain a valid token. The input does not specify whether exploitation requires network or local access, authentication, or user interaction.
Teams running Maven package io.jenkins:configuration-as-code at versions >=1.55 <1.55.1, >=1.54 <1.54.1, >=1.48 <1.53.1, or <1.47.1 should check their installations.