Information Exposure Through Log Files Affecting jenkins package, versions *


Severity

Recommended
0.0
low
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.39% (32nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-JENKINS-9891212
  • published28 Apr 2025
  • disclosed11 Oct 2017

Introduced: 11 Oct 2017

CVE-2017-1000401  (opens in a new tab)
CWE-532  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 jenkins.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jenkins package and not the jenkins package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

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.