Improper input validation in Jenkins

CVE-2017-1000401

The Jenkins 2.73.1 and earlier, 2.83 and earlier default form control for passwords and other secrets, <f:password/>, supports form validation (e.g. for API keys). The form validation AJAX requests were sent via GET, which could result in secrets being logged to a HTTP access log in non-default configurations of Jenkins, and made available to users with access to these log files. Form validation for <f:password/> is now always sent via POST, which is typically not logged.

Vulnerability class: Drupalgeddon 2 (CVE-2018-7600)

Published · last modified .

CVSS v3 metric

CVSS v3 base score 2.2 (Low). Vector: CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N.

EPSS exploit prediction

EPSS: 0.004 (30.7th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 31st percentile — 30.7% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2017-1000401: held from 0.004 to 0.004.

EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: 0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2017-1000401?
CVE-2017-1000401 is a low-severity vulnerability in Jenkins, classified under Improper Input Validation. CVSS score: 2.2/10. Published 2018-01-26.
How severe is CVE-2017-1000401?
Low severity. CVSS v3 base score is 2.2 out of 10.
Is CVE-2017-1000401 known to be exploited?
1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.