Executive brief
The Jenkins Job Configuration History Plugin, which tracks changes to job and agent settings, fails to hide sensitive encrypted data in its history logs. This allows users with limited read-only access to view encrypted secrets, such as authentication tokens, which they should not be able to see. While the data is encrypted, exposing these values increases the risk of credential theft or unauthorized access if the encryption can be bypassed.
Technical details
The Job Configuration History Plugin (up to version 1356.ve360da_6c523a_) fails to redact encrypted secret values when displaying historical job and agent configurations. This occurs specifically within the 'View as XML' (RAW) feature and the configuration diff views. An attacker with 'Item/Extended Read' permissions—who normally should not have access to sensitive configuration details—can view these encrypted strings (e.g., build trigger tokens). While the values remain encrypted, Jenkins security policy typically requires these to be redacted for users without 'Item/Configure' permissions to prevent offline attacks or accidental exposure. The vulnerability is tracked as SECURITY-3742.
Affected products
- Jenkins Project Job Configuration History Plugin 1356.ve360da_6c523a_ and earlier
Timeline
- 2026-06-24: disclosed: Advisory published by Jenkins Project