Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsUpgrade @bitcoin-js/tiny-secp256k1-asmjs to version 2.2.5 or higher.
@bitcoin-js/tiny-secp256k1-asmjs is an A tiny secp256k1 JS
Affected versions of this package are vulnerable to Unchecked Return Value via the three-argument form of xOnlyPointAddTweakCheck in index.ts, which ignores the failure return value from the wasm backend when a tweak produces the point at infinity. The shared X_ONLY_PUBLIC_KEY_INPUT buffer is left unchanged after the failed call, still holding the original point, so a caller who passes resultToCheck equal to that point causes the stale-buffer comparison to return true even though no valid tweaked key exists. Protocols that rely on this helper to validate caller-controlled internal keys, tweaks, and comparison values can therefore accept an invalid derived key.