Private-key extraction via bypassed message type check
Published Jul 1, 2025 · Updated Jul 1, 2025
Cryptographic key disclosure in BitcoinJS tiny-secp256k1 before 1.1.7 allows remote attackers to extract a private key via a crafted message. The signing path trusts a bypassable Buffer.isBuffer result, so a malicious JSON-stringifiable object causes ECDSA nonce reuse across different messages. Exploitation requires a bundle using the npm buffer package to sign one attacker-controlled message and access to a second message-signature pair.
Summary
What happened
Cryptographic key disclosure in BitcoinJS tiny-secp256k1 before 1.1.7 allows remote attackers to extract a private key via a crafted message. The signing path trusts a bypassable Buffer.isBuffer result, so a malicious JSON-stringifiable object causes ECDSA nonce reuse across different messages. Exploitation requires a bundle using the npm buffer package to sign one attacker-controlled message and access to a second message-signature pair.
The record
- CVE
- CVE-2024-49364
- Published
- Jul 1, 2025
- Updated
- Jul 1, 2025
- Vendor
- BitcoinJS
- Product
- tiny-secp256k1
- Classifications
- CWE-522, T1552.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 1, 2025CVE publishedPublication date reported by the CVE source.
- Jul 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.1.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo