CVE-2017-2602

LOWNVD 3.1

3.1

jenkins before versions 2.44, 2.32.2 is vulnerable to an improper blacklisting of the Pipeline metadata files in the agent-to-master security subsystem. This could allow metadata files to be written to by malicious agents (SECURITY-358).

CVSS v3: 3.1
EG Score: —
EPSS: 37.1%
KEV: Not listed

Published

May 15, 2018

Last Modified

November 21, 2024

References (8)

secalert@redhathttp://www.securityfocus.com/bid/95952
secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2602
secalert@redhathttps://github.com/jenkinsci/jenkins/commit/414ff7e30aba66bed18c4ee8a8660fb36fc8c655
secalert@redhathttps://jenkins.io/security/advisory/2017-02-01/
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/95952
af854a3a-2127-422b-91ae-364da2661108https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2602
af854a3a-2127-422b-91ae-364da2661108https://github.com/jenkinsci/jenkins/commit/414ff7e30aba66bed18c4ee8a8660fb36fc8c655
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(1)

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

CWE-184Incomplete List of Disallowed Inputs

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-2602?

CVE-2017-2602 is a low vulnerability published on May 15, 2018. jenkins before versions 2.44, 2.32.2 is vulnerable to an improper blacklisting of the Pipeline metadata files in the agent-to-master security subsystem. This could allow metadata files to be written to by malicious agents (SECURITY-358).

When was CVE-2017-2602 disclosed?

CVE-2017-2602 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-2602 actively exploited?

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

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

CVE-2017-2602 has a CVSS v3 base score of 3.1 (NVD).

How do I remediate CVE-2017-2602?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-2602, 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-2602

Explore →

Is Your Infrastructure Affected by CVE-2017-2602?

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

Start Free Scan →Browse All CVEs