CVE-2024-48930Public exploitNetwork attack vector

Private-key extraction via unchecked compressed curve points

Published Oct 21, 2024 · Updated Oct 21, 2024

Improper public-key validation in secp256k1-node before 3.8.1, 4.0.0 through 4.0.3, and 5.0.0 allows remote attackers to extract private keys. loadCompressedPublicKey reconstructs a Y coordinate from attacker-controlled X data without verifying that the resulting point lies on secp256k1, admitting low-order points from other curves. After 11 ECDH sessions, predictable outputs reveal enough remainders to recover the private key; the elliptic implementation must process crafted compressed keys.

CVSS severity8.7
High
EPSS probability0.41%
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 public-key validation in secp256k1-node before 3.8.1, 4.0.0 through 4.0.3, and 5.0.0 allows remote attackers to extract private keys. loadCompressedPublicKey reconstructs a Y coordinate from attacker-controlled X data without verifying that the resulting point lies on secp256k1, admitting low-order points from other curves. After 11 ECDH sessions, predictable outputs reveal enough remainders to recover the private key; the elliptic implementation must process crafted compressed keys.

The record

CVE
CVE-2024-48930
Published
Oct 21, 2024
Updated
Oct 21, 2024
Vendor
cryptocoinjs
Product
secp256k1-node
Classifications
CWE-200, CWE-354, T1552.004
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Oct 21, 2024CVE publishedPublication date reported by the CVE source.
  2. Oct 21, 2024Record 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=0 <3.8.1
  2. Affected versionversion=< 3.8.1
  3. Affected versionversion=>= 4.0.0, < 4.0.4
  4. Affected versionversion=4.0.0 <4.0.4
  5. Affected versionversion== 5.0.0
  6. Affected versionversion=5.0.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

cryptocoinjs · secp256k1-nodeversion=0 <3.8.1; version=< 3.8.1; version=>= 4.0.0, < 4.0.4; version=4.0.0 <4.0.4; version== 5.0.0; version=5.0.0

Published CVSS scores

8.7GitHubCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

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-200Exposure of Sensitive Information to an Unauthorized Actor
CWE-354Improper Validation of Integrity Check Value
T1552.004Private Keys

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