Skip to content
Fencer Intel
high 8.0

CVE-2023-35141 json

Jenkins CSRF protection bypass vulnerability

published 3y ago modified 2mo ago also BIT-jenkins-2023-35141 , EUVD-2023-1762 , GHSA-98fp-r22g-wpj7

cvss
8.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

In Jenkins 2.399 and earlier, LTS 2.387.3 and earlier, POST requests are sent in order to load the list of context actions. If part of the URL includes insufficiently escaped user-provided values, a victim may be tricked into sending a POST request to an unexpected endpoint by opening a context menu.

Patch / fix

  • maven org.jenkins-ci.main:jenkins-core 2.400
  • bitnami jenkins 2.401.1
  • Jenkins Project Jenkins 2.400

Is CVE-2023-35141 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2023-35141 updated cvss 8.0

jenkins: CSRF protection bypass vulnerability

  • Red Hat OpenShift Container Platform 3.11 jenkins
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Container Platform 4 jenkins
    affected: no fix available
  • Red Hat Cryostat 2 jenkins Red Hat Node HealthCheck Operator jenkins Red Hat OpenShift Developer Tools and Services 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.86% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-14).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
GitHub 3.1 8.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 8.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
CNA 3.1 8.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
OSV 3.1 8.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.main:jenkins-core
<2.400
2.400
bitnami jenkins
<2.401.1
2.401.1

Affected products

  • Jenkins Project Jenkins

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery
Technology feeds

References

Sources

Fencer Intel 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.