Skip to content
Fencer Intel
high 7.3

CVE-2017-1000391 json

Improper Input Validation in Jenkins

published 8y ago modified 4mo ago also GHSA-wfj3-535m-p6fx , EUVD-2022-5563

cvss
7.3
version 3.0, NVD
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

Jenkins versions 2.88 and earlier and 2.73.2 and earlier stores metadata related to 'people', which encompasses actual user accounts, as well as users appearing in SCM, in directories corresponding to the user ID on disk. These directories used the user ID for their name without additional escaping, potentially resulting in problems like overwriting of unrelated configuration files.

Patch / fix

  • maven org.jenkins-ci.main:jenkins-core 2.73.3, 2.89

Is CVE-2017-1000391 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-1000391 updated cvss 3.7

jenkins: Unsafe use of user names as directory names

  • Red Hat OpenShift Enterprise 3 jenkins
    affected: no fix planned “Will not fix”

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.50% 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
NVD 3.0 7.3 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H
NVD 2.0 4.9 AV:N/AC:M/Au:S/C:N/I:P/A:P
GitHub 3.0 7.3 CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.main:jenkins-core
<2.73.3
>=2.74, <2.89
2.73.3
2.89

Classification

Weakness
  • CWE-20 Improper Input Validation
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.