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.
{
"nvd_published_at": "2022-06-23T17:15:00Z",
"cwe_ids": [
"CWE-203",
"CWE-208"
],
"severity": "MODERATE",
"github_reviewed": true,
"github_reviewed_at": "2022-12-05T23:37:15Z"
}