Skip to content
Fencer Intel
medium 5.4

CVE-2017-2613 json

Cross-Site Request Forgery in Jenkins

published 2018-05-15 8 y ago modified 2026-06-17 4 mo ago also GHSA-pwv6-872c-gcg6 , EUVD-2022-4844

cvss
5.4
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

jenkins before versions 2.44, 2.32.2 is vulnerable to a user creation CSRF using GET by admins. While this user record was only retained until restart in most cases, administrators' web browsers could be manipulated to create a large number of user records (SECURITY-406).

Patch / fix

  • maven org.jenkins-ci.main:jenkins-core 2.32.2, 2.44
  • jenkins jenkins 2.32.2, 2.44

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-2017-2613 updated cvss 5.4

jenkins: User creation CSRF using GET by admins (SECURITY-406)

  • Red Hat OpenShift Enterprise 2 jenkins Red Hat OpenShift Enterprise 3 jenkins
    under investigation

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.60% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 5.4 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
NVD 3.0 5.4 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:N/I:P/A:P
GitHub 3.0 5.4 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.main:jenkins-core
<2.32.2
>=2.34, <2.44
2.32.2
2.44

Affected products

  • [UNKNOWN] jenkins

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling
  • 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.