CVE-2017-2612

MEDIUMNVD 5.4

5.4

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.

CVSS v3: 5.4
EG Score: —
EPSS: 30.4%
KEV: Not listed

Published

May 15, 2018

Last Modified

November 21, 2024

References (8)

secalert@redhathttp://www.securityfocus.com/bid/95957
secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2612
secalert@redhathttps://github.com/jenkinsci/jenkins/commit/a814154695e23dc37542af7d40cacc129cf70722
secalert@redhathttps://jenkins.io/security/advisory/2017-02-01/
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/95957
af854a3a-2127-422b-91ae-364da2661108https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2612
af854a3a-2127-422b-91ae-364da2661108https://github.com/jenkinsci/jenkins/commit/a814154695e23dc37542af7d40cacc129cf70722
af854a3a-2127-422b-91ae-364da2661108https://jenkins.io/security/advisory/2017-02-01/

Affected Packages

(1 across 1 ecosystem)

Maven(1)

Package	Vulnerable range	Fixed in	Dependents
org.jenkins-ci.main:jenkins-core	2.34 ... 2.43 (10 versions)	2.44	—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 05:16 UTCOSV refresh

Frequently asked(5)

What is CVE-2017-2612?

CVE-2017-2612 is a medium vulnerability published on May 15, 2018. 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.

When was CVE-2017-2612 disclosed?

CVE-2017-2612 was first published in the National Vulnerability Database on May 15, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2017-2612 actively exploited?

CVE-2017-2612 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 30.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2017-2612?

CVE-2017-2612 has a CVSS v3 base score of 5.4 (NVD).

How do I remediate CVE-2017-2612?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-2612, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-2612

Explore →

Is Your Infrastructure Affected by CVE-2017-2612?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs