advisory-db/crates/cggmp24/RUSTSEC-2025-0128.md

[advisory]
id = "RUSTSEC-2025-0128"
package = "cggmp24"
date = "2025-11-24"
url = "https://www.dfns.co/article/cggmp21-vulnerabilities-patched-and-explained"
categories = ["crypto-failure"]
keywords = ["hd-wallet", "presignature", "tss"]
aliases = ["CVE-2025-66017", "GHSA-8frv-q972-9rq5"]
[versions]
patched = [">= 0.7.0-alpha.2"]

CGGMP21 presignatures can be used in the way that significantly reduces security

This attack is against presignatures used in very specific context:

• Presignatures + HD wallets derivation: security level reduces to 85 bits
  Previously you could generate a presignature, and then choose a HD derivation path while issuing a partial signature via Presignature::set_derivation_path, which is malleable to attack that reduces target security level. To mitigate, this method has been removed from API.
• Presignatures + "raw signing" (when signer signs a hash without knowing an original message): results into signature forgery attack
  Previously, you could use Presignature::issue_partial_signature with hashed message without ever providing original mesage. In new API, this method only accepts digests for which original message has been observed.

Patches

cggmp24 v0.7.0-alpha.2 release contains API changes that make it impossible to use presignatures in contexts in which it reduces security. Follow the migration guidelines to upgrade.

Workarounds

You can continue using un-patched versions of library as long as you don't use presignatures in said scenarios where it weakens system security. To be sure, migrate to patched version that excludes presignatures from being used in such scenarios.

References

Read our blog post to learn more.