The Jenkins 2.73.1 and earlier, 2.83 and earlier default form control for passwords and other secrets, &lt;f:password/&gt;, 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 &lt;f:password/&gt; is now always sent via POST, which is typically not logged.
This is a vulnerability exploitable with only local access requires the attacker to have either
physical access to the vulnerable system or a local (shell) account. Examples of locally
exploitable vulnerabilities are peripheral attacks such as Firewire/USB DMA attacks, and
local privilege escalations (e.g., sudo).
Specialized access conditions exist. For example,
in most configurations, the attacking party must already have elevated privileges or spoof additional systems
in addition to the attacking system (e.g., DNS hijacking).
The attack depends on social engineering methods that would be easily detected by knowledgeable people.
For example, the victim must perform several suspicious or atypical actions.
The vulnerable configuration is seen very rarely in practice.
If a race condition exists, the window is very narrow.
Authentication is not required to access and exploit the vulnerability.
There is considerable informational disclosure. Access to some system files is
possible, but the attacker does not have control over what is obtained, or the scope of
the loss is constrained. An example is a vulnerability that divulges only certain tables
in a database.
There is no impact to the integrity of the system.
There is no impact to the availability of the system.