Skip to content

Observable timing discrepancy allows determining username validity in Jenkins

Moderate severity GitHub Reviewed Published Jun 24, 2022 to the GitHub Advisory Database • Updated Dec 27, 2023

Package

maven org.jenkins-ci.main:jenkins-core (Maven)

Affected versions

>= 2.334, < 2.356
< 2.332.4

Patched versions

2.356
2.332.4

Description

In Jenkins 2.355 and earlier, LTS 2.332.3 and earlier, an observable timing discrepancy on the login form allows distinguishing between login attempts with an invalid username, and login attempts with a valid username and wrong password, when using the Jenkins user database security realm. This allows attackers to determine the validity of attacker-specified usernames.

Login attempts with an invalid username now validate a synthetic password to eliminate the timing discrepancy in Jenkins 2.356, LTS 2.332.4.

References

Published by the National Vulnerability Database Jun 23, 2022
Published to the GitHub Advisory Database Jun 24, 2022
Reviewed Dec 5, 2022
Last updated Dec 27, 2023

Severity

Moderate

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
Low
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:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.150%
(52nd percentile)

Weaknesses

CVE ID

CVE-2022-34174

GHSA ID

GHSA-9grj-j43m-mjqr

Source code

Credits

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