GHSA-36f9-7rg5-cpf8: `@bsv/wallet-toolbox` / `-client` / `-mobile` don't verify storage-supplied recipient output scripts against
Source: github.com
Reported by @echennells (Eric Chennells). Migrated from public issue #191 to a private advisory. Affected: @bsv/wallet-toolbox / -client / -mobile. Verified in 2.1.21 and 2.1.21-parity-fix.2; the relevant code is the same at current HEAD Summary: When createAction runs against a remote StorageClient, the storage server returns the outputs to build. buildSignableTransaction takes each non-change output's lockingScript from the storage response and signs it, without comparing it to the lockingScript the caller supplied in args.outputs. …
Signalsas the pipeline stamped them
High High-risk vulnerability
CVEKEV and EPSS where known
Get the next one first
Every story goes to Telegram and RSS the moment it is published, and the whole wire is a keyless JSON API.