Description
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.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | node-yarnpkg | No fix yet | — |
| Ubuntu 26.04 LTS | node-yarnpkg | No fix yet | — |
| Ubuntu 25.10 | node-yarnpkg | No fix yet | — |
| Ubuntu 24.04 LTS | node-yarnpkg | No fix yet | — |
| Ubuntu 22.04 LTS | node-yarnpkg | No fix yet | — |
Show 1 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 20.04 LTS | node-yarnpkg | No fix yet | — |
References
- https://github.com/yarnpkg/website/commits/master
- 20190430 OpenPGP and S/MIME signature forgery attacks in multiple email clients mailing-list
- http://packetstormsecurity.com/files/152703/Johnny-You-Are-Fired.html
- [oss-security] 20190430 Spoofing OpenPGP and S/MIME Signatures in Emails (multiple clients) mailing-list
- https://github.com/RUB-NDS/Johnny-You-Are-Fired
- https://github.com/RUB-NDS/Johnny-You-Are-Fired/blob/master/paper/johnny-fired.pdf