Skip to content
Fencer Intel
medium 5.4

CVE-2017-2612 json

Incorrect Permission Assignment for Critical Resource in Jenkins

published 8y ago modified 4mo ago also GHSA-wf9g-rh76-6jvr , EUVD-2022-5562

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

Summary

In Jenkins before versions 2.44, 2.32.2 low privilege users were able to override JDK download credentials (SECURITY-392), resulting in future builds possibly failing to download a JDK.

Patch / fix

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

Is CVE-2017-2612 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-2017-2612 updated cvss 5.4

jenkins: Low privilege users were able to override JDK download credentials (SECURITY-392)

  • 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.49% chance of exploitation in the next 30 days, higher than 74% 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:L/UI:N/S:U/C:N/I:L/A:L
NVD 3.0 5.4 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
NVD 2.0 5.5 AV:N/AC:L/Au:S/C:N/I:P/A:P
GitHub 3.0 5.4 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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-358 Improperly Implemented Security Check for Standard
  • CWE-732 Incorrect Permission Assignment for Critical Resource
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.