CVE-2024-49365Public exploitNetwork attack vector

Signature verification bypass via spoofed Buffer objects

Published Jul 1, 2025 · Updated Jul 1, 2025

Improper cryptographic signature verification in BitcoinJS tiny-secp256k1 before 1.1.7 allows remote attackers to authenticate crafted messages. The verify() path relies on the npm buffer package's spoofable Buffer.isBuffer check, so JSON-compatible objects pass as messages and yield false-positive true results. Exploitation requires a browser-bundled or React Native environment using that Buffer implementation plus a known valid message-signature pair; the result is acceptance of attacker-chosen message content.

CVSS severityUnavailable
Unscored
EPSS probability0.22%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper cryptographic signature verification in BitcoinJS tiny-secp256k1 before 1.1.7 allows remote attackers to authenticate crafted messages. The verify() path relies on the npm buffer package's spoofable Buffer.isBuffer check, so JSON-compatible objects pass as messages and yield false-positive true results. Exploitation requires a browser-bundled or React Native environment using that Buffer implementation plus a known valid message-signature pair; the result is acceptance of attacker-chosen message content.

The record

CVE
CVE-2024-49365
Published
Jul 1, 2025
Updated
Jul 1, 2025
Vendor
BitcoinJS
Product
tiny-secp256k1
Classifications
CWE-347
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 1, 2025CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=< 1.1.7

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

BitcoinJS · tiny-secp256k1version=< 1.1.7

Published CVSS scores

8.1GitHub CNACVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature

Public exploit references

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