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-62514: CWE-327: Use of a Broken or Risky Cryptographic Algorithm in Scille parsec-cloud

0
High
VulnerabilityCVE-2025-62514cvecve-2025-62514cwe-327cwe-1240
Published: Thu Jan 29 2026 (01/29/2026, 15:46:50 UTC)
Source: CVE Database V5
Vendor/Project: Scille
Product: parsec-cloud

Description

CVE-2025-62514 is a high-severity cryptographic vulnerability affecting the Parsec web application versions 3. 0. 0-alpha up to but not including 3. 6. 0. The issue arises from the use of a risky cryptographic algorithm implementation in the RustCrypto backend of libparsec_crypto, which fails to check for weak order points in Curve25519 during the Diffie-Hellman key exchange. This flaw allows a man-in-the-middle attacker to manipulate the key exchange, causing both parties to derive the same shared key known to the attacker, thereby compromising confidentiality and integrity without alerting users. The Parsec desktop application is not affected as it uses a different backend (libsodium). No known exploits are currently in the wild, and the vulnerability is patched in version 3. 6.

AI-Powered Analysis

AILast updated: 01/29/2026, 16:12:13 UTC

Technical Analysis

CVE-2025-62514 identifies a cryptographic vulnerability in the Parsec cloud-based file sharing application, specifically in the libparsec_crypto component when compiled with the RustCrypto backend. The vulnerability stems from the failure to validate weak order points on Curve25519 during the Diffie-Hellman key exchange process. Curve25519 is widely used for secure key exchange due to its resistance to certain cryptographic attacks; however, weak order points can undermine this security by enabling an attacker positioned as a man-in-the-middle (MITM) to inject specially crafted points. This manipulation causes both communicating parties to derive the same shared secret key that is also known to the attacker, effectively breaking the confidentiality and integrity of the communication. The attack bypasses the SAS (Short Authentication String) code verification, misleading users into believing the exchange is secure. The vulnerability affects only the Parsec web client versions from 3.0.0-alpha up to 3.6.0, as the desktop client uses libsodium, which does not exhibit this flaw. The vulnerability has a CVSS v3.1 score of 8.3 (high severity), reflecting its network attack vector, low complexity, requirement for privileges but no user interaction, and significant impact on confidentiality and integrity with limited availability impact. Although no exploits are currently known in the wild, the vulnerability poses a serious risk to secure file sharing environments relying on Parsec web. The issue was reserved in October 2025 and published in January 2026, with a patch released in version 3.6.0 that presumably includes proper validation of Curve25519 points to prevent weak order point attacks.

Potential Impact

For European organizations, this vulnerability threatens the confidentiality and integrity of sensitive data shared via the Parsec web client. An attacker capable of intercepting network traffic (e.g., on public or compromised networks) can perform a MITM attack to decrypt or manipulate files exchanged, potentially leading to data breaches, intellectual property theft, or regulatory non-compliance under GDPR. The integrity compromise can also facilitate injection of malicious content or unauthorized data modifications. Availability impact is low but secondary effects such as loss of trust or operational disruptions may occur. Sectors with high reliance on secure cloud file sharing, such as finance, healthcare, legal, and government agencies, are particularly vulnerable. The vulnerability's exploitation could undermine secure collaboration and data exchange workflows, increasing the risk of espionage or sabotage. Since Parsec is a niche but growing secure file sharing solution, organizations that have adopted it without upgrading to the fixed version remain exposed. The attack requires network-level access but no user interaction, making it feasible in targeted or opportunistic scenarios, especially in environments with insufficient network segmentation or monitoring.

Mitigation Recommendations

The primary mitigation is to upgrade all Parsec web clients to version 3.6.0 or later, where the vulnerability is patched. Organizations should audit their deployment to identify any use of the vulnerable RustCrypto backend and confirm that no legacy versions remain in use. Network defenses should be enhanced to detect and prevent MITM attacks, including the use of strong TLS configurations, certificate pinning, and network segmentation. Employing endpoint detection and response (EDR) tools to monitor unusual cryptographic operations or network anomalies can help identify exploitation attempts. Additionally, organizations should review their cryptographic libraries and ensure they use well-vetted backends like libsodium where possible. User training to recognize suspicious network behavior and enforcing secure VPN or zero-trust network access can reduce exposure. Finally, implementing multi-factor authentication and robust logging for file sharing activities will aid in early detection and response to potential compromises.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-10-15T15:03:28.134Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 697b837eac063202229a57ed

Added to database: 1/29/2026, 3:57:50 PM

Last enriched: 1/29/2026, 4:12:13 PM

Last updated: 1/29/2026, 5:56:01 PM

Views: 4

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 more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats