CVE-2017-2599

MEDIUMNVD 5.4

5.4

Jenkins before versions 2.44 and 2.32.2 is vulnerable to an insufficient permission check. This allows users with permissions to create new items (e.g. jobs) to overwrite existing items they don't have access to (SECURITY-321).

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

Published

April 11, 2018

Last Modified

November 21, 2024

References (8)

secalert@redhathttp://www.securityfocus.com/bid/95949
secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2599
secalert@redhathttps://github.com/jenkinsci/jenkins/commit/4ed5c850b6855ab064a66d02fb338f366853ce89
secalert@redhathttps://jenkins.io/security/advisory/2017-02-01/
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/95949
af854a3a-2127-422b-91ae-364da2661108https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-2599
af854a3a-2127-422b-91ae-364da2661108https://github.com/jenkinsci/jenkins/commit/4ed5c850b6855ab064a66d02fb338f366853ce89
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-863Incorrect Authorization

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-25 17:16 UTCOSV refresh

Frequently asked(5)

What is CVE-2017-2599?

CVE-2017-2599 is a medium vulnerability published on April 11, 2018. Jenkins before versions 2.44 and 2.32.2 is vulnerable to an insufficient permission check. This allows users with permissions to create new items (e.g. jobs) to overwrite existing items they don't have access to (SECURITY-321).

When was CVE-2017-2599 disclosed?

CVE-2017-2599 was first published in the National Vulnerability Database on April 11, 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-2599 actively exploited?

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

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

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

How do I remediate CVE-2017-2599?

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

Explore →

Is Your Infrastructure Affected by CVE-2017-2599?

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

Start Free Scan →Browse All CVEs