bitcoinj: ScriptExecution P2PKH/P2WPKH Verification Bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| bitcoinj | bitcoinj | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Bitcoinj | Bitcoinj |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-hfcf-v2f8-x9pc | bitcoinj has a ScriptExecution P2PKH/P2WPKH Verification Bypass |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.270% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Bitcoinj
Bitcoinj bitcoinj |
|
| Vendors & Products |
Bitcoinj
Bitcoinj bitcoinj |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The bitcoinj library is a Java implementation of the Bitcoin protocol. Prior to 0.17.1, ScriptExecution.correctlySpends() contains two fast-path verification bugs for standard P2PKH and native P2WPKH spends in core/src/main/java/org/bitcoinj/script/ScriptExecution.java. In both branches, bitcoinj verifies an attacker-controlled signature/public-key pair but fails to verify that the public key is the one committed to by the output being spent. As a result, any attacker keypair can satisfy bitcoinj's local verification for arbitrary P2PKH and P2WPKH outputs. This vulnerability is fixed in 0.17.1. | |
| Title | bitcoinj: ScriptExecution P2PKH/P2WPKH Verification Bypass | |
| Weaknesses | CWE-347 | |
| References |
| |
| Metrics |
cvssV3_1
|