tiny-secp256k1 invalid tweak acceptance in xOnlyPointAddTweakCheck
bitcoinjs tiny-secp256k1 · @bitcoin-js iny-secp256k1-asmjs
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| bitcoinjs tiny-secp256k1 |
| No fix yet |
| @bitcoin-js iny-secp256k1-asmjs |
| No fix yet |
Original description
tiny-secp256k1 is a tiny secp256k1 native/JS wrapper. From 2.1.0 until 2.2.5 for tiny-secp256k1 and from 2.2.2 until 2.2.5 for @bitcoin-js/tiny-secp256k1-asmjs, the three-argument xOnlyPointAddTweakCheck path ignores the backend failure return from xOnlyPointAddTweak when a tweak produces the point at infinity. The shared X_ONLY_PUBLIC_KEY_INPUT buffer then still contains the original point, so a caller-controlled resultToCheck equal to that point can make the stale-buffer comparison return true even though no tweaked key exists. Protocols that rely on this helper to validate caller-controlled internal keys, tweaks, and comparison values can accept an invalid derived key. This issue is fixed in version 2.2.5.