Improper input validation in Jenkins
CVE-2017-1000401
- CVSS v3
- 2.2 Low
- Public exploits
- None known
- EPSS
- 0.004 · 33.8th percentile
- Published
- 2018-01-26
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.
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.
- Attack Vector
- Local
AV:L - Attack Complexity
- High
AC:H - Privileges Required
- Low
PR:L - User Interaction
- Required
UI:R - Scope
- Unchanged
S:U - Confidentiality
- Low
C:L - Integrity
- None
I:N - Availability
- None
A:N
EPSS exploit prediction
EPSS 0.004, 33.8th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (ARPSyndicate/cvemon). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- jenkins.io/security/advisory/2017-10-11/ (Vendor Advisory)