notation-go's verification bypass can cause users to verify the wrong artifact
High severity
GitHub Reviewed
Published
Jun 6, 2023
in
notaryproject/notation-go
•
Updated Nov 8, 2023
Package
Affected versions
< 1.0.0-rc.6
Patched versions
1.0.0-rc.6
Description
Published to the GitHub Advisory Database
Jun 6, 2023
Reviewed
Jun 6, 2023
Published by the National Vulnerability Database
Jun 6, 2023
Last updated
Nov 8, 2023
Credits
-
AdamKorcz Analyst
-
shizhMSFT Analyst
-
priteshbandi Analyst
Impact
An attacker who controls or compromises a registry can lead a user to verify the wrong artifact.
Patches
The problem has been fixed in the release v1.0.0-rc.6. Users should upgrade their notation-go library to v1.0.0-rc.6 or above.
Workarounds
User should use secure and trusted container registries.
Credits
The
notationproject would like to thank Adam Korczynski (@AdamKorcz) for responsibly disclosing the issue found during an security audit (facilitated by OSTIF and sponsored by CNCF) and Shiwei Zhang (@shizhMSFT), Pritesh Bandi (@priteshbandi) for root cause analysis.References