-
Bug
-
Resolution: Fixed
-
Critical
-
1.89 in 1.554.2
If you have a BuildWrapper which overrides makeSensitiveBuildVariables to specify that its additions are to be considered secret, then add an EnvInjectBuilder which adds some unrelated variables, injectedEnvVars.txt includes the sensitive variables (in plaintext) and /job/.../.../injectedEnvVars/ shows them as well.
- is blocking
-
JENKINS-23630 Update to new environment variable APIs
-
- Resolved
-
- is related to
-
JENKINS-12423 Password masked by Mask Passwords are visible when using envinject plugin
-
- Closed
-
-
JENKINS-4428 MavenProbeAction exposes password parameters
-
- Resolved
-
-
JENKINS-24287 EnvInject exposes password hashes
-
- Resolved
-
For example install the Credentials Binding plugin (1.0 just released), create a global username/password credentials, then make a job binding those credentials to $AUTH, and add an EnvInject build step adding some other variable, and a shell step running env. Both variables will be set correctly, but injectedEnvVars will show AUTH=user:pass in cleartext despite build.getSensitiveBuildVariables().contains("AUTH").