First published: Tue Nov 15 2022(Updated: )
A flaw was found in the script-security Jenkins Plugin. SHA-1 no longer meets the security standards for producing a cryptographically secure message digest. The affected version of the script-security Plugin stores whole-script approvals as the SHA-1 hash of the approved script.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/jenkins | <2-plugins-0:4.10.1675144701-1.el8 | 2-plugins-0:4.10.1675144701-1.el8 |
redhat/jenkins | <2-plugins-0:4.9.1675668922-1.el8 | 2-plugins-0:4.9.1675668922-1.el8 |
Jenkins Script Security | <1190.v65867a_a_47126 | |
<1190.v65867a_a_47126 | ||
redhat/Script Security Plugin | <1190. | 1190. |
maven/org.jenkins-ci.plugins:script-security | <=1189.vb | 1190.v65867a_a_47126 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-45379 is classified as a high-severity vulnerability due to the use of SHA-1 for script approval in Jenkins.
To fix CVE-2022-45379, upgrade the Jenkins Script Security Plugin and Jenkins to the recommended versions or later.
CVE-2022-45379 affects Jenkins installations with the script-security plugin versions prior to 1190.v65867a_a_47126.
CVE-2022-45379 impacts the security of script approvals by using the outdated SHA-1 hashing algorithm.
Currently, there is no known effective workaround for CVE-2022-45379, so upgrading is strongly advised.