Skip to main content

CVE-2025-58359: CWE-325: Missing Cryptographic Step in ZcashFoundation frost

Medium
VulnerabilityCVE-2025-58359cvecve-2025-58359cwe-325
Published: Thu Sep 04 2025 (09/04/2025, 23:50:45 UTC)
Source: CVE Database V5
Vendor/Project: ZcashFoundation
Product: frost

Description

ZF FROST is a Rust implementation of FROST (Flexible Round-Optimised Schnorr Threshold signatures). In versions 2.0.0 through 2.1.0, refresh shares with smaller min_signers will reduce security of group. The inability to change min_signers (i.e. the threshold) with the refresh share functionality (frost_core::keys::refresh module) was not made clear to users. Using a smaller value would not decrease the threshold, and attempts to sign using a smaller threshold would fail. Additionally, after refreshing the shares with a smaller threshold, it would still be possible to sign with the original threshold, potentially causing a security loss to the participant's shares. This issue is fixed in version 2.2.0.

AI-Powered Analysis

AILast updated: 09/05/2025, 16:10:26 UTC

Technical Analysis

CVE-2025-58359 is a medium-severity vulnerability affecting versions 2.0.0 through 2.1.0 of ZF FROST, a Rust implementation of the Flexible Round-Optimised Schnorr Threshold (FROST) signature scheme developed by the Zcash Foundation. The vulnerability arises from a missing cryptographic step related to the refresh share functionality within the frost_core::keys::refresh module. Specifically, the implementation does not allow the threshold parameter (min_signers) to be effectively lowered when refreshing shares. Although users might attempt to reduce the threshold to require fewer signers for signature generation, the system does not enforce this change; signing attempts with a smaller threshold fail, but signing with the original threshold remains possible. This discrepancy can lead to a security loss because participants' shares may be exposed or weakened if the threshold is misunderstood or misused. The core issue is a lack of clarity and enforcement around threshold changes during share refresh operations, which can undermine the intended security guarantees of threshold signatures. The vulnerability is fixed in version 2.2.0 of the library. The CVSS 4.0 score is 6.0 (medium), reflecting network attack vector, low attack complexity, partial authentication required, no user interaction, and high impact on confidentiality but no impact on integrity or availability. No known exploits are reported in the wild as of the publication date.

Potential Impact

For European organizations leveraging ZF FROST for cryptographic operations, particularly those relying on threshold signatures for securing multi-party authorization or distributed key management, this vulnerability could weaken the security model. An attacker or malicious insider with partial access could exploit the misunderstanding or misuse of the threshold parameter to reduce the effective security threshold, potentially enabling unauthorized signing or key compromise. This could lead to unauthorized transactions, data signing, or other cryptographic operations being performed without the intended quorum, undermining trust in critical systems such as blockchain infrastructures, secure communications, or financial services. Given the high confidentiality impact, sensitive cryptographic keys or signatures could be exposed or forged. However, the requirement for partial authentication and the absence of user interaction reduces the likelihood of widespread exploitation. The lack of known exploits suggests limited active threat but does not preclude targeted attacks. Organizations in sectors such as finance, blockchain technology, and secure communications in Europe should be particularly vigilant.

Mitigation Recommendations

European organizations using ZF FROST should immediately upgrade to version 2.2.0 or later, where the vulnerability is fixed. Prior to upgrading, they should audit their use of the refresh share functionality to ensure that threshold parameters have not been improperly lowered or misconfigured. Implement strict operational procedures and code reviews around threshold changes to prevent misuse. Additionally, organizations should monitor cryptographic operations for anomalies indicating unauthorized signing attempts or threshold misuse. Where possible, implement multi-factor authentication and enhanced logging around key management operations. For critical deployments, consider additional cryptographic safeguards or alternative threshold signature implementations until the patch is applied. Engage with the Zcash Foundation or maintainers for guidance on secure upgrade paths and best practices. Finally, conduct security awareness training for developers and operators on the nuances of threshold signature schemes and the importance of correct parameter management.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2025-08-29T16:19:59.010Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68bb0b63cc26dbd53247d4ad

Added to database: 9/5/2025, 4:10:11 PM

Last enriched: 9/5/2025, 4:10:26 PM

Last updated: 9/5/2025, 4:10:35 PM

Views: 2

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

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