GHSA-9grj-j43m-mjqr

Observable timing discrepancy allows determining username validity in Jenkins

At a glance

Published
Updated
CVE
CVE-2022-34174
Aliases
BIT-jenkins-2022-34174
CVSS_V3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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.

Affected packages

PackageVersions
Maven · org.jenkins-ci.main:jenkins-coreintroduced 2.334, fixed 2.356
Maven · org.jenkins-ci.main:jenkins-coreintroduced 0, fixed 2.332.4

References

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database