github.com/binance-chain/tss-lib vulnerabilities
- Registry
- Go
- Latest
- 1.3.5
9 known advisories
The latest version, 1.3.5, is affected by 7 of them.
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
Security advisories for github.com/binance-chain/tss-lib
Incorrect Default Permissions in Binance tss-lib in github.com/binance-chain/tss-lib
- Affected
- <1.2.0
- Fixed in
- 1.2.0
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
Incorrect Default Permissions in Binance tss-lib
- Affected
- <1.2.0
- Fixed in
- 1.2.0
Is your github.com/binance-chain/tss-lib version vulnerable?
Which of your client projects still run an old github.com/binance-chain/tss-lib?
NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Go packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.