dbcve.org
JenkinsApplication

CVE-2022-34174

HIGH · 7.5 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 2.355 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Jenkins versions 2.355 and earlier, and LTS 2.332.3 and earlier, contain a timing-based information disclosure vulnerability in the login form. When using Jenkins' internal user database for authentication, the application exhibits measurably different response times between attempts with invalid usernames versus valid usernames with incorrect passwords, allowing attackers to enumerate valid user accounts through timing analysis.

MitigationUpgrade Jenkins to version 2.356 or later, or LTS 2.332.4 or later, which contain the fix for uniform timing. As a temporary workaround, consider using external authentication mechanisms (LDAP, SAML) which are not affected by this vulnerability in the same manner.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JenkinsApplication
Affected:<= 2.332.3<= 2.355

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jenkins version
    Navigate to Manage Jenkins > About Jenkins or check the version displayed on the login page. Compare against the affected versions: 2.332.3 and earlier (LTS), or 2.355 and earlier.
    Affected if The installed version is 2.332.3 or earlier, or 2.355 or earlier.
  2. Confirm internal user database is in use
    Navigate to Manage Jenkins > Global Security > Authentication. Check the 'Security Realm' setting. If it shows 'Jenkins own user database', the internal database is being used.
    Affected if The Security Realm is set to Jenkins own user database.
  3. Verify uniform timing is implemented
    Review the Jenkins version. Versions 2.356 and later, or LTS 2.332.4 and later, contain the fix for uniform timing in the login form.
    Affected if The version is earlier than 2.356 (or earlier than 2.332.4 LTS) AND internal user database is in use.

You are affected if you run Jenkins version 2.332.3 or earlier (LTS), or 2.355 or earlier, AND have Jenkins internal user database selected as the Security Realm.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.355
Interim mitigation

Upgrade Jenkins to version 2.356 or later, or LTS 2.332.4 or later, which contain the fix for uniform timing. As a temporary workaround, consider using external authentication mechanisms (LDAP, SAML) which are not affected by this vulnerability in the same manner.

Recommended fix High confidence

Jenkins 2.356 (weekly) or Jenkins LTS 2.332.4

  1. 1. Backup your Jenkins home directory and configuration before upgrading.
  2. 2. Stop the Jenkins service.
  3. 3. Download Jenkins 2.356 (weekly release) or Jenkins LTS 2.332.4 from the official Jenkins downloads page (www.jenkins.io/download).
  4. 4. Replace the jenkins.war file in your Jenkins installation directory with the new version.
  5. 5. Start the Jenkins service.
  6. 6. Verify the login behavior no longer reveals timing differences between invalid usernames and wrong passwords for valid usernames.
  7. 7. Confirm all plugins are still functioning correctly after the upgrade.
Caveat Review plugin compatibility before upgrading, as some plugins may require updates for these Jenkins versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34174 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34174 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data