CVE-2022-34174: In Jenkins 2.355 and earlier, LTS 2.332.3 and earlier, an observable timing discrepancy on the login form allows distinguishing between logi
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 76.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: org.jenkins-ci.main:jenkins-core (Maven) 2.356, 2.332.4; jenkins (Red Hat:openshift:4.10::el8) 0:2.361.1.1675406172-1.el8; jenkins-2-plugins (Red Hat:openshift:4.10::el8) 0:4.10.1675407676-1.el8.
Low priority for now. Upgrade to org.jenkins-ci.main:jenkins-core (Maven) 2.356, 2.332.4; jenkins (Red Hat:openshift:4.10::el8) 0:2.361.1.1675406172-1.el8; jenkins-2-plugins (Red Hat:openshift:4.10::el8) 0:4.10.1675407676-1.el8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 23, 2022
- Updated
- Jun 17, 2026
- EPSS
- 1.6% · 76th percentile
- CWE
- CWE-203
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| jenkins | jenkins | cpe:2.3:a:jenkins:jenkins |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jenkins jenkinsup to 2.332.3 inclusive
- jenkins jenkinsup to 2.355 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (jenkins). Independent of NVD's CPE analysis and usually ahead of it.
Jenkins project Jenkins
- unspecified and later · up to and including 2.355affected
- unspecified and later · up to and including LTS 2.332.3affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.jenkins-ci.main:jenkins-core | from 2.334 · before 2.356 | 2.356 |
| Maven | org.jenkins-ci.main:jenkins-core | before 2.332.4 | 2.332.4 |
| Red Hat:openshift:4.10::el8 | jenkins | before 0:2.361.1.1675406172-1.el8 | 0:2.361.1.1675406172-1.el8 |
| Red Hat:openshift:4.10::el8 | jenkins-2-plugins | before 0:4.10.1675407676-1.el8 | 0:4.10.1675407676-1.el8 |
| Red Hat:openshift:4.8::el8 | jenkins | before 0:2.361.1.1672840472-1.el8 | 0:2.361.1.1672840472-1.el8 |
| Red Hat:openshift:4.8::el8 | jenkins-2-plugins | before 0:4.8.1672842762-1.el8 | 0:4.8.1672842762-1.el8 |
| Red Hat:openshift:4.9::el8 | jenkins | before 0:2.361.1.1675668150-1.el8 | 0:2.361.1.1675668150-1.el8 |
| Red Hat:openshift:4.9::el8 | jenkins-2-plugins | before 0:4.9.1675668922-1.el8 | 0:4.9.1675668922-1.el8 |
Same product
jenkins: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-23897Jenkins 2.441 and earlier, LTS 2.426.2 and earlier does not disable a feature of its CLI command parser that replaces an '@' character folloKEV99Now
- CVE-2017-1000353Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to an unauthenticated remote code execution.KEV99Now
- CVE-2018-1000861A code execution vulnerability exists in the Stapler web framework used by Jenkins 2.153 and earlier, LTS 2.138.3 and earlier in stapler/corKEV98Now
Published before and after this one in the same product
- ← EarlierCVE-2022-34172Jun 23, 2022 · In Jenkins 2.340 through 2.355 (both inclusive) symbol-based icons unescape previously escaped values of 'tooltip' parameters, resulting in 21Monitor
- ← EarlierCVE-2022-34173Jun 23, 2022 · In Jenkins 2.340 through 2.355 (both inclusive) the tooltip of the build button in list views supports HTML without escaping the job display21Monitor
- Later →CVE-2022-34175Jun 23, 2022 · Jenkins 2.335 through 2.355 (both inclusive) allows attackers in some cases to bypass a protection mechanism, thereby directly accessing som30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.jenkins-ci.main:jenkins-core | 2.332.4 | Package registry (OSV) |
| Maven:org.jenkins-ci.main:jenkins-core | 2.356 | Package registry (OSV) |
| red hat:jenkins | 0:2.361.1.1672840472-1.el8 · Red Hat:openshift:4.8::el8 | Package registry (OSV) |
| red hat:jenkins-2-plugins | 0:4.8.1672842762-1.el8 · Red Hat:openshift:4.8::el8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-203 · Observable DiscrepancyCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.