tss-lib leaks secret keys in response to incorrectly constructed Paillier moduli

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact The specification of the GG18 threshold ECDSA signature protocol contains a vulnerability allowing an attacker to recover the shared secret key. If a participant generates a Paillier modulus N containing small factors (less than 2^100) they can interact with other participants in the signing protocol to steal their secret key shares in as little as sixteen signing attempts. The master key can then be reconstructed from these shares. Patches The implementation of GG18 in tss-lib did not prove that N is biprime or that it doesn't contain small factors. The fixed implementation adds the following proofs from the CGGMP21 threshold ECDSA protocol to the key generation: - Paillier-Blum Modulus (N is the product of two primes) - No Small Factor (both factors of N are greater than 2^256) These proofs apply to both the Paillier encryption modulus N, and the modulus NTilde used in MTA proofs. To address the issue in the resharing protocol, an additional round has been added to the end…

Published by the source

1 Sep 2023, 20:51 UTC

Last modified by the source

1 Sep 2023, 20:51 UTC

Source last checked

26 Oct 2026, 14:59 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h24c-6p6p-m3vx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-h24c-6p6p-m3vx

Advisory: tss-lib leaks secret keys in response to incorrectly constructed Paillier moduli
IDs: GHSA-h24c-6p6p-m3vx
Record: https://patchnext.com/advisories/ghsa-h24c-6p6p-m3vx (revision 1, source checked 26 Oct 2026, 14:59 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/bnb-chain/tss-lib: affected <= 1.3.5

## Suggested inspection (read-only)
- Go github.com/bnb-chain/tss-lib: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/bnb-chain/tss-lib.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h24c-6p6p-m3vx (GitHub-reviewed advisory GHSA-h24c-6p6p-m3vx lists affected ranges: Go github.com/bnb-chain/tss-lib >=0 <=1.3.5)

Commands are suggestions: review each one before running it.