Advisory

GHSA-hc36-c89j-5f4j

Details, part 2 of 2. The advisory

Details

Consumers should upgrade whichever gem they depend on directly; they do not need both. bsv-wallet 0.3.4 additionally tightens its dependency on bsv-sdk from the stale ~> 0.4 to >= 0.8.2, < 1.0, which forces the known-good pairing and pulls in the sibling advisory fixes (F1.3, F5.13) tracked separately.

The issuance-path fix also partially closes finding F8.16 from the same compliance review. F8.16's second aspect — switching the issuance transport from ad-hoc JSON POST to BRC-104 AuthFetch — is not addressed here and remains deferred to a future release.

Fixed in sgbett/bsv-ruby-sdk#306.

Workarounds

If upgrading is not immediately possible:

  • Do not expose acquire_certificate (either acquisition protocol) to untrusted callers.
  • Do not invoke acquire_certificate with acquisition_protocol: 'issuance' against a certifier URL you do not fully trust, and require TLS for any such request.
  • Treat any record returned by list_certificates / prove_certificate as unverified and perform an out-of-band BRC-52 verification against the certifier's public key before acting on it.

Credit

Identified during the 2026-04-08 cross-SDK compliance review, tracked as findings F8.15 (direct path) and F8.16 (issuance path, partial).

References

  • HLR: sgbett/bsv-ruby-sdk#305
  • Fix PR: sgbett/bsv-ruby-sdk#306
  • Compliance review: [.architecture/reviews/20260408-cross-sdk-compliance-review.md](../../.architecture/reviews/20260408-cross-sdk-compliance-review.md)
  • BRC-52 specification: https://brc.dev/52
  • TypeScript reference: Certificate.verify() in @bsv/sdk

Sources & licences