Bsv Wallet
Approved changes feed: RSS · Atom
cpe:2.3:a:sgbett:bsv-wallet:*:*:*:*:*:ruby:*:*
part: a version: * update: *
| Vendor | Sgbett (ee7a9b63-825e-5d9d-8201-c959f8fe8811) |
|---|---|
| Product | Bsv Wallet (61fb1c58-e82e-572b-844b-757b7dbbabe4) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | ruby |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:gem/bsv-wallet |
purl2cpe | 2026-07-28 16:41:15.180229 |
pkg:github/sgbett/bsv-ruby-sdk |
purl2cpe | 2026-07-28 16:41:15.180230 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-40070 |
vulnerable | 2026-06-08 08:01:19.855442 |
bsv-sdk and bsv-wallet persist unverified certifier signatures in acquire_certificate (direct and issuance paths)
HIGH (8.1)
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.
Published: 2026-04-09T17:26:51.495Z
Updated: 2026-04-13T15:38:58.154Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.