Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-66017: CWE-327: Use of a Broken or Risky Cryptographic Algorithm in LFDT-Lockness cggmp21

0
High
VulnerabilityCVE-2025-66017cvecve-2025-66017cwe-327
Published: Tue Nov 25 2025 (11/25/2025, 19:59:07 UTC)
Source: CVE Database V5
Vendor/Project: LFDT-Lockness
Product: cggmp21

Description

CGGMP24 is a state-of-art ECDSA TSS protocol that supports 1-round signing (requires 3 preprocessing rounds), identifiable abort, and a key refresh protocol. In versions 0.6.3 and prior of cggmp21 and version 0.7.0-alpha.1 of cggmp24, presignatures can be used in the way that significantly reduces security. cggmp24 version 0.7.0-alpha.2 release contains API changes that make it impossible to use presignatures in contexts in which it reduces security.

AI-Powered Analysis

AILast updated: 11/25/2025, 20:20:03 UTC

Technical Analysis

CVE-2025-66017 identifies a cryptographic vulnerability in the LFDT-Lockness cggmp21 (<= 0.6.3) and cggmp24 (0.7.0-alpha.1) libraries, which implement an advanced ECDSA Threshold Signature Scheme (TSS) protocol. This protocol supports efficient 1-round signing with preprocessing and includes features like identifiable abort and key refresh. However, in the affected versions, the handling of presignatures—precomputed signature components intended to optimize signing—can be misused in a manner that significantly weakens the cryptographic security guarantees. Specifically, the vulnerability stems from the use of a broken or risky cryptographic algorithm (CWE-327), which undermines the integrity of the signature process. The flaw allows an attacker to exploit presignatures to potentially forge signatures or compromise the threshold signing process without requiring authentication or user interaction, and can be exploited remotely over the network. The vulnerability has been addressed in cggmp24 version 0.7.0-alpha.2, which introduces API changes that prevent presignatures from being used insecurely. Despite the absence of known exploits in the wild, the high CVSS 8.7 score reflects the critical nature of the cryptographic weakness and the potential for severe impact if exploited.

Potential Impact

For European organizations, especially those involved in financial services, government, telecommunications, and critical infrastructure, this vulnerability poses a significant risk. The compromised cryptographic integrity could lead to unauthorized signature forgeries, undermining trust in digital transactions, secure communications, and identity verification processes. This may result in data breaches, fraudulent transactions, and loss of regulatory compliance, particularly under GDPR and other data protection frameworks. Organizations using the affected cggmp21 or cggmp24 libraries in their security-critical applications could face operational disruptions and reputational damage. The remote and unauthenticated nature of the exploit increases the attack surface, making it easier for threat actors to target vulnerable systems across Europe. Given the strategic importance of secure cryptographic protocols in sectors like banking, government, and technology, the impact could be widespread if not promptly mitigated.

Mitigation Recommendations

European organizations should immediately audit their software supply chains and internal applications to identify usage of the affected cggmp21 (<= 0.6.3) and cggmp24 (0.7.0-alpha.1) versions. The primary mitigation is to upgrade to cggmp24 version 0.7.0-alpha.2 or later, which contains API changes that eliminate insecure presignature usage. Where upgrading is not immediately feasible, organizations should implement strict controls to prevent the use of presignatures in vulnerable contexts, including code reviews and runtime monitoring for suspicious cryptographic operations. Additionally, organizations should enforce network-level protections such as segmentation and intrusion detection systems tuned to detect anomalous cryptographic traffic patterns. Cryptographic key management policies should be reviewed and strengthened to include key rotation and revocation procedures in case of compromise. Finally, organizations should monitor threat intelligence feeds for any emerging exploits related to this vulnerability and prepare incident response plans accordingly.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-21T01:08:02.613Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69260c0cffc41f183f7e2ce2

Added to database: 11/25/2025, 8:05:32 PM

Last enriched: 11/25/2025, 8:20:03 PM

Last updated: 11/25/2025, 9:06:30 PM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats