Skip to content

Observable Discrepancy and Observable Timing Discrepancy in Jenkins Configuration as Code Plugin

Low severity GitHub Reviewed Published Jan 21, 2022 to the GitHub Advisory Database • Updated Dec 27, 2023

Package

maven io.jenkins:configuration-as-code (Maven)

Affected versions

= 1.55
= 1.54
>= 1.48, < 1.53.1
< 1.47.1

Patched versions

1.55.1
1.54.1
1.53.1
1.47.1

Description

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.

References

Published by the National Vulnerability Database Jan 12, 2022
Reviewed Jan 20, 2022
Published to the GitHub Advisory Database Jan 21, 2022
Last updated Dec 27, 2023

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.071%
(33rd percentile)

Weaknesses

CVE ID

CVE-2022-23106

GHSA ID

GHSA-fpj7-9xm6-8hgr

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.