What is the severity of CVE-2017-1000401?

CVE-2017-1000401 has a medium severity rating due to the potential exposure of sensitive information through HTTP access logs.

How do I fix CVE-2017-1000401?

To fix CVE-2017-1000401, upgrade Jenkins to version 2.73.2 or 2.83.1 or later.

What are the affected versions in CVE-2017-1000401?

CVE-2017-1000401 affects Jenkins versions 2.73.1 and earlier, as well as 2.83 and earlier.

What does CVE-2017-1000401 entail?

CVE-2017-1000401 involves the leakage of secrets through GET requests in form validation, which can lead to sensitive information being logged.

Is CVE-2017-1000401 a critical vulnerability?

CVE-2017-1000401 is not classified as critical; it is considered medium severity and thus should be addressed but is not an immediate threat.

Vulnerability/
CVE-2017-1000401

low

2.2

CWE

26/1/2018

5/8/2024

CVE-2017-1000401: Input Validation

First published: Fri Jan 26 2018(Updated: )

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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Jenkins Jenkins	<=2.73.1
Jenkins Jenkins	<=2.83

Never miss a vulnerability like this again

Reference Links

https://jenkins.io/security/advisory/2017-10-11/

Frequently Asked Questions

What is the severity of CVE-2017-1000401?
CVE-2017-1000401 has a medium severity rating due to the potential exposure of sensitive information through HTTP access logs.
How do I fix CVE-2017-1000401?
To fix CVE-2017-1000401, upgrade Jenkins to version 2.73.2 or 2.83.1 or later.
What are the affected versions in CVE-2017-1000401?
CVE-2017-1000401 affects Jenkins versions 2.73.1 and earlier, as well as 2.83 and earlier.
What does CVE-2017-1000401 entail?
CVE-2017-1000401 involves the leakage of secrets through GET requests in form validation, which can lead to sensitive information being logged.
Is CVE-2017-1000401 a critical vulnerability?
CVE-2017-1000401 is not classified as critical; it is considered medium severity and thus should be addressed but is not an immediate threat.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/references
agent/weakness
agent/last-modified-date
agent/author
agent/description
agent/tags
agent/event
agent/first-publish-date
agent/source
vendor/jenkins
canonical/jenkins jenkins
version/jenkins jenkins/2.73.1
version/jenkins jenkins/2.83

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-1000401?
CVE-2017-1000401 has a medium severity rating due to the potential exposure of sensitive information through HTTP access logs.
How do I fix CVE-2017-1000401?
To fix CVE-2017-1000401, upgrade Jenkins to version 2.73.2 or 2.83.1 or later.
What are the affected versions in CVE-2017-1000401?
CVE-2017-1000401 affects Jenkins versions 2.73.1 and earlier, as well as 2.83 and earlier.
What does CVE-2017-1000401 entail?
CVE-2017-1000401 involves the leakage of secrets through GET requests in form validation, which can lead to sensitive information being logged.
Is CVE-2017-1000401 a critical vulnerability?
CVE-2017-1000401 is not classified as critical; it is considered medium severity and thus should be addressed but is not an immediate threat.