Skip to content

Whole-script approval in Jenkins Script Security Plugin vulnerable to SHA-1 collisions

High severity GitHub Reviewed Published Nov 16, 2022 to the GitHub Advisory Database • Updated Jan 4, 2024

Package

maven org.jenkins-ci.plugins:script-security (Maven)

Affected versions

<= 1189.vb

Patched versions

1190.v65867a_a_47126

Description

Script Security Plugin 1189.vb_a_b_7c8fd5fde and earlier stores whole-script approvals as the SHA-1 hash of the approved script. SHA-1 no longer meets the security standards for producing a cryptographically secure message digest.

Script Security Plugin 1190.v65867a_a_47126 uses SHA-512 for new whole-script approvals. Previously approved scripts will have their SHA-1 based whole-script approval replaced with a corresponding SHA-512 whole-script approval when the script is next used.

Whole-script approval only stores the SHA-1 or SHA-512 hash, so it is not possible to migrate all previously approved scripts automatically on startup.

Administrators concerned about SHA-1 collision attacks on the whole-script approval feature are able to revoke all previous (SHA-1) script approvals on the In-Process Script Approval page.

References

Published by the National Vulnerability Database Nov 15, 2022
Published to the GitHub Advisory Database Nov 16, 2022
Reviewed Nov 21, 2022
Last updated Jan 4, 2024

Severity

High
8.0
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

CVE ID

CVE-2022-45379

GHSA ID

GHSA-fv42-mx39-6fpw

Credits

Checking history
See something to contribute? Suggest improvements for this vulnerability.