This weekExploitable · Confirmed
tiny-secp256k1: tiny-secp256k1 allows for verify() bypass when running in bundled environment
There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.
Does it affect what I run?
tiny-secp256k1 (npm)
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- tiny-secp256k1 (npm): every version, before 1.1.7
The fix
tiny-secp256k1 (npm) fixed in 1.1.7
npmnpm install tiny-secp256k1@1.1.7pnpmpnpm add tiny-secp256k1@1.1.7yarnyarn add tiny-secp256k1@1.1.7bunbun add tiny-secp256k1@1.1.7Check what is installednpm ls tiny-secp256k1Paste into Cursor, Lovable or Claude CodeUpgrade the npm dependency tiny-secp256k1 to 1.1.7 or the nearest later release, to fix CVE-2024-49365. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
Exploitable · Confirmed
CISA's assessment in the CVE record says a proof of concept is public.
CISA Vulnrichment (SSVC and KEV fields inside CVE records)Stated
Timeline
- First published here, as "For your digest".
- Level changed from "For your digest" to "This week".
- Evidence added: CISA's assessment in the CVE record says a proof of concept is public. (CISA Vulnrichment (SSVC and KEV fields inside CVE records))