tiny-secp256k1 allows for verify() bypass when running in bundled environment
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| bitcoinjs | tiny-secp256k1 | affected |
|
No data.
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-54991 | tiny-secp256k1 allows for verify() bypass when running in bundled environment |
Github GHSA |
GHSA-5vhg-9xg4-cv9m | tiny-secp256k1 allows for verify() bypass when running in bundled environment |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.247% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | tiny-secp256k1 is a tiny secp256k1 native/JS wrapper. Prior to version 1.1.7, a malicious JSON-stringifyable message can be made passing on verify(), when global Buffer is the buffer package. This affects only environments where require('buffer') is the NPM buffer package. Buffer.isBuffer check can be bypassed, resulting in strange objects being accepted as a message, and those messages could trick verify() into returning false-positive true values. This issue has been patched in version 1.1.7. | |
| Title | tiny-secp256k1 allows for verify() bypass when running in bundled environment | |
| Weaknesses | CWE-347 | |
| References |
| |
| Metrics |
cvssV4_0
|
No data.