When creating secret file credentials Plain Credentials Plugin 182.v468b_97b_9dcb_8 and earlier attempts to decrypt the content of the file to check if it constitutes a valid encrypted secret. In rare cases the file content matches the expected format of an encrypted secret, and the file content will be stored unencrypted (only Base64 encoded) on the Jenkins controller file system.
These credentials can be viewed by users with access to the Jenkins controller file system (global credentials) or with Item/Extended Read permission (folder-scoped credentials).
Plain Credentials Plugin 183.va_de8f1dd5a_2b_ no longer attempts to decrypt the content of the file when creating secret file credentials.
References:- https://nvd.nist.gov/vuln/detail/CVE-2024-39459
- https://www.jenkins.io/security/advisory/2024-06-26/#SECURITY-2495
- http://www.openwall.com/lists/oss-security/2024/06/26/2
- https://github.com/jenkinsci/plain-credentials-plugin/commit/ade8f1dd5a2bc69357995fd50baac56d73f80813
- https://github.com/advisories/GHSA-3cpq-rw36-cppv