CVE-2022-47930: GO-2023-1867 - Replay attacks involving proofs in github.com/bnb-chain/tss-lib

CVE-2022-47930 · Severity: low · CVSS 3.1 · Published 2023-07-11

Replay attacks involving proofs in github.com/bnb-chain/tss-lib

Technologies: github.com/binance-chain/tss-lib (Go), github.com/bnb-chain/tss-lib (Go). Vendors: Go.

Quick answers

Is CVE-2022-47930 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-47930 being exploited in the wild.
How severe is CVE-2022-47930?
Low severity, with a CVSS score of 3.1, published 11 July 2023.
Which products and versions are affected?
github.com/binance-chain/tss-lib (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.0.0; github.com/bnb-chain/tss-lib (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.0.0.
Is there a fix for CVE-2022-47930?
Yes. github.com/binance-chain/tss-lib (Go): upgrade to 2.0.0 or later; github.com/bnb-chain/tss-lib (Go): upgrade to 2.0.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-47930?
Check whether you run github.com/binance-chain/tss-lib (Go) or github.com/bnb-chain/tss-lib (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/binance-chain/tss-lib (Go): upgrade to 2.0.0 or later
    go get github.com/binance-chain/tss-lib@v2.0.0
  • github.com/bnb-chain/tss-lib (Go): upgrade to 2.0.0 or later
    go get github.com/bnb-chain/tss-lib@v2.0.0

Affected products

  • github.com/binance-chain/tss-lib (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.0.0
  • github.com/bnb-chain/tss-lib (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=2.0.0

Identifiers

  • CVE-2022-47930
  • GHSA-c58h-qv6g-fw74
  • GO-2023-1867

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.