dbcve.org
JenkinsApplication

CVE-2022-34175

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
Jenkins 2.335 through 2.355 (both inclusive) allows attackers in some cases to bypass a protection mechanism, thereby directly accessing some view fragments containing sensitive information, bypassing any permission checks in the corresponding view.

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.335 through 2.355 contain a protection mechanism bypass vulnerability that allows unauthenticated or low-privilege attackers in some cases to directly access view fragments containing sensitive information, bypassing the normal permission checks enforced by the view.

MitigationUpgrade Jenkins to version 2.356 or later. Before upgrading, backup the Jenkins instance and test the upgrade in a non-production environment to ensure compatibility with existing plugins and jobs.

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.335, <= 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. Check installed Jenkins version
    Navigate to Manage Jenkins > About Jenkins in the web UI, or run 'java -jar jenkins.war --version' from the command line if you have CLI access
    Affected if Installed version is 2.335, 2.336, 2.337, 2.338, 2.339, 2.340, 2.341, 2.342, 2.343, 2.344, 2.345, 2.346, 2.347, 2.348, 2.349, 2.350, 2.351, 2.352, 2.353, 2.354, or 2.355
  2. Verify if anonymous access is enabled
    Go to Manage Jenkins > Configure Global Security and check the Authorization section to see if Anonymous read access is granted
    Affected if Anonymous users have any level of access to views or job information
  3. Determine if low-privilege users can access views
    Go to Manage Jenkins > Configure Global Security > Authorization and check if users with Overall/Read or limited permissions can navigate to custom views
    Affected if Users with limited permissions (below Admin) can access custom or system views
  4. Review existing custom views for sensitive content
    Click through each view tab in Jenkins and identify any that display credentials, secrets, sensitive build logs, or configuration details
    Affected if Custom views exist that may display sensitive information that should be protected

The environment is affected if Jenkins version is 2.335 through 2.355 AND the instance allows unauthenticated or low-privilege users to access views that may contain sensitive information.

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. Before upgrading, backup the Jenkins instance and test the upgrade in a non-production environment to ensure compatibility with existing plugins and jobs.

Recommended fix High confidence

Jenkins 2.356 or later (weekly release), or the next LTS release after 2.355

  1. Check current Jenkins version by navigating to Manage Jenkins > About Jenkins
  2. Review plugin compatibility with newer Jenkins versions before upgrading
  3. Back up Jenkins home directory (JENKINS_HOME) including all configurations and job data
  4. Schedule a maintenance window for the upgrade
  5. Download Jenkins 2.356 or later from the official Jenkins website (https://www.jenkins.io/download/)
  6. Upgrade Jenkins by deploying the new WAR file or using your package manager
  7. Start Jenkins and monitor startup logs for errors
  8. Verify all critical jobs and pipelines function correctly after upgrade
Caveat Review Jenkins LTS upgrade guide for potential breaking changes between 2.335-2.355 and the target version; some plugins may require updates

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

Fix this in Jenkins Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34175 — 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-34175 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