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)
EPSS: 0.004 (31.8th percentile) — read the EPSS interpretation.
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.
Affected products
- Jenkins
- N/a — versions n/a
Weakness classification (CWE)
Public proof-of-concept exploits
References
- cve@mitre.org (x_refsource_CONFIRM, Vendor Advisory)
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.