bsv-sdk and bsv-wallet persist unverified certifier signatures in acquire_certificate (direct and issuance paths)
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| sgbett | bsv-ruby-sdk | affected |
|
||||||
| sgbett | bsv-sdk | affected |
|
||||||
| sgbett | bsv-wallet | affected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Sgbett | Bsv-ruby-sdk |
|
||||||||
| Sgbett | Bsv-sdk |
|
||||||||
| Sgbett | Bsv-wallet |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-hc36-c89j-5f4j | bsv-sdk and bsv-wallet persist unverified certifier signatures in acquire_certificate (direct and issuance paths) |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.138% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Sgbett bsv Ruby Sdk
|
|
| CPEs | cpe:2.3:a:sgbett:bsv-wallet:*:*:*:*:*:ruby:*:* cpe:2.3:a:sgbett:bsv_ruby_sdk:*:*:*:*:*:ruby:*:* |
|
| Vendors & Products |
Sgbett bsv Ruby Sdk
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Sgbett
Sgbett bsv-ruby-sdk Sgbett bsv-sdk Sgbett bsv-wallet |
|
| Vendors & Products |
Sgbett
Sgbett bsv-ruby-sdk Sgbett bsv-sdk Sgbett bsv-wallet |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | BSV Ruby SDK is the Ruby SDK for the BSV blockchain. From 0.3.1 to before 0.8.2, BSV::Wallet::WalletClient#acquire_certificate persists certificate records to storage without verifying the certifier's signature over the certificate contents. In acquisition_protocol: 'direct', the caller supplies all certificate fields (including signature:) and the record is written to storage verbatim. In acquisition_protocol: 'issuance', the client POSTs to a certifier URL and writes whatever signature the response body contains, also without verification. An attacker who can reach either API (or who controls a certifier endpoint targeted by the issuance path) can forge identity certificates that subsequently appear authentic to list_certificates and prove_certificate. | |
| Title | bsv-sdk and bsv-wallet persist unverified certifier signatures in acquire_certificate (direct and issuance paths) | |
| Weaknesses | CWE-347 | |
| References |
| |
| Metrics |
cvssV3_1
|