Is github.com/binance-chain/tss-lib 1.3 vulnerable?
Go · 5 releases from 1.3.0 to 1.3.5 · latest github.com/binance-chain/tss-lib is 1.3.5 · checked 18 Nov 2026
Yes: 7 known advisories
Yes. github.com/binance-chain/tss-lib 1.3.5, the last 1.3 release, is affected by 7 known security advisories (1 critical, 1 high, 1 medium, 4 low), including CVE-2023-26556, CVE-2023-26557, CVE-2022-47930. At least one has no fixed release yet.
Is your project on an affected github.com/binance-chain/tss-lib?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/binance-chain/tss-lib 1.3.5
Timing attack from non-constant time scalar arithmetic in github.com/bnb-chain/tss-lib
- Affected
- All versions
- Fixed in
- No fix released
Collision of hash values in github.com/bnb-chain/tss-lib
- Affected
- All versions
- Fixed in
- No fix released
Replay attacks involving proofs in github.com/bnb-chain/tss-lib
- Affected
- All versions
- Fixed in
- No fix released
Timing attack from non-constant time scalar multiplication in github.com/bnb-chain/tss-lib
- Affected
- All versions
- Fixed in
- No fix released
IO FinNet tss-lib vulnerable to timing attack from non-constant time scalar multiplication
- Affected
- <2.0.0
- Fixed in
- 2.0.0
IO FinNet tss-lib vulnerable to timing attack from non-constant time scalar arithmetic
- Affected
- <1.3.6-0.20230324145555-bb6fb30bd3eb
- Fixed in
- 1.3.6-0.20230324145555-bb6fb30bd3eb
IO FinNet tss-lib vulnerable to replay attacks involving proofs
- Affected
- <2.0.0
- Fixed in
- 2.0.0
Every github.com/binance-chain/tss-lib 1.3.x release
Affected: 1.3.0 to 1.3.5.
| Version | Known advisories |
|---|---|
| github.com/binance-chain/tss-lib 1.3.5 | CVE-2023-26557, CVE-2022-47931, CVE-2022-47930, CVE-2023-26556, CVE-2023-26556, CVE-2023-26557, CVE-2022-47930 |
| github.com/binance-chain/tss-lib 1.3.3 | CVE-2023-26557, CVE-2022-47931, CVE-2022-47930, CVE-2023-26556, CVE-2023-26556, CVE-2023-26557, CVE-2022-47930 |
| github.com/binance-chain/tss-lib 1.3.2 | CVE-2023-26557, CVE-2022-47931, CVE-2022-47930, CVE-2023-26556, CVE-2023-26556, CVE-2023-26557, CVE-2022-47930 |
| github.com/binance-chain/tss-lib 1.3.1 | CVE-2023-26557, CVE-2022-47931, CVE-2022-47930, CVE-2023-26556, CVE-2023-26556, CVE-2023-26557, CVE-2022-47930 |
| github.com/binance-chain/tss-lib 1.3.0 | CVE-2023-26557, CVE-2022-47931, CVE-2022-47930, CVE-2023-26556, CVE-2023-26556, CVE-2023-26557, CVE-2022-47930 |
Which of your client projects are still on github.com/binance-chain/tss-lib 1.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/binance-chain/tss-lib version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/binance-chain/tss-lib versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.