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.
Advisories
Source ID Title
EUVD EUVD EUVD-2022-4107 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.
Github GHSA Github GHSA GHSA-h8c5-c92g-jq6x Improper Input Validation in Jenkins
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-05T22:00:40.945Z

Reserved: 2017-11-29T00:00:00

Link: CVE-2017-1000401

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2018-01-26T02:29:01.203

Modified: 2024-11-21T03:04:38.963

Link: CVE-2017-1000401

cve-icon Redhat

Severity : Low

Publid Date: 2017-10-11T00:00:00Z

Links: CVE-2017-1000401 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses