cryptocoinjs secp256k1-node up to 3.8.0/4.0.3/5.0.0 publicKeyVerify integrity check

Summaryinfo

A vulnerability was found in cryptocoinjs secp256k1-node up to 3.8.0/4.0.3/5.0.0 and classified as problematic. Affected by this vulnerability is the function publicKeyVerify. Such manipulation leads to integrity check. This vulnerability is listed as CVE-2024-48930. The attack may be performed from remote. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in cryptocoinjs secp256k1-node up to 3.8.0/4.0.3/5.0.0 and classified as problematic. Affected by this issue is the function publicKeyVerify. The manipulation with an unknown input leads to a integrity check vulnerability. Using CWE to declare the problem leads to CWE-354. The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission. Impacted is confidentiality. CVE summarizes:

secp256k1-node is a Node.js binding for an Optimized C library for EC operations on curve secp256k1. In `elliptic`-based version, `loadUncompressedPublicKey` has a check that the public key is on the curve. Prior to versions 5.0.1, 4.0.4, and 3.8.1, however, `loadCompressedPublicKey` is missing that check. That allows the attacker to use public keys on low-cardinality curves to extract enough information to fully restore the private key from as little as 11 ECDH sessions, and very cheaply on compute power. Other operations on public keys are also affected, including e.g. `publicKeyVerify()` incorrectly returning `true` on those invalid keys, and e.g. `publicKeyTweakMul()` also returning predictable outcomes allowing to restore the tweak. Versions 5.0.1, 4.0.4, and 3.8.1 contain a fix for the issue.

The advisory is available at github.com. This vulnerability is handled as CVE-2024-48930 since 10/10/2024. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit.

Upgrading to version 3.8.1, 4.0.4 or 5.0.1 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• cryptocoinjs

Name

• secp256k1-node

Version

• 3.0
• 3.1
• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7
• 3.8.0
• 4.0.0
• 4.0.1
• 4.0.2
• 4.0.3
• 5.0

Website

• Product: https://github.com/cryptocoinjs/secp256k1-node/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion