Skip to content
Fencer Vulns
high 7.5

CVE-2022-34175 json

Unauthorized view fragment access in Jenkins

published 2022-06-22 4 y ago modified 2026-09-08 2 mo ago also BIT-jenkins-2022-34175 , EUVD-2022-6103 , GHSA-p3rc-946h-8cf5

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.jenkins-ci.main:jenkins-core 2.356
  • bitnami jenkins 2.355.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-34175 updated cvss 7.5

Jenkins: Unauthorized view fragment access

  • Red Hat OpenShift Container Platform 3.11 jenkins Red Hat OpenShift Container Platform 4 jenkins
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.40% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.main:jenkins-core
>=2.335, <2.356
2.356
bitnami jenkins
>=2.335.0, <2.355.1
2.355.1

Affected products

  • Jenkins project Jenkins

Classification

Weakness
  • CWE-693 Protection Mechanism Failure
  • CWE-863 Incorrect Authorization
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.