The signature verification routine in install.sh in yarnpkg/website through 2018-06-05 only verifies that the yarn release is signed by any (arbitrary) key in the local keyring of the user, and does not pin the signature to the yarn release key, which allows remote attackers to sign tampered yarn release packages with their own key.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: mitre
Published: 2019-05-16T16:12:53
Updated: 2024-08-05T08:38:06.342Z
Reserved: 2018-06-18T00:00:00
Link: CVE-2018-12556
Vulnrichment
No data.
NVD
Status : Modified
Published: 2019-05-16T17:29:00.730
Modified: 2024-11-21T03:45:25.750
Link: CVE-2018-12556
Redhat
No data.