Cryptocurrency flaws called 'BitForge' expose crypto wallets to theft
Take action: Knowing that your wallet is at risk of theft is not great news. While the vulnerabilities are still not exploited in the wild, it's wise to start checking for an update of the software for your wallet. Or distribute the risk by transferring some of the files to another patched wallet.
Learn More
A series of critical security vulnerabilities in widely used cryptographic protocols, collectively named 'BitForge,' have been discovered by cryptography researchers. The BitForge vulnerabilities specifically target the implementation of cryptographic protocols such as GG-18, GG-20, and Lindell 17. These protocols are fundamental to the concept of multi-party computation (MPC) wallets, which allow multiple parties to generate keys and co-sign transactions collaboratively.
These vulnerabilities have impacted several popular cryptocurrency wallet providers, including Coinbase, ZenGo, Binance, and others. These security flaws could potentially allow hackers to steal digital assets from these wallets with remarkable ease, without requiring any user or vendor interaction.
Researchers unveiled the BitForge vulnerabilities on a presentation at the BlackHat conference. Coinbase and ZenGo acted swiftly to address and rectify the issues within their systems. However, other major wallet providers, notably Binance, and numerous smaller projects remain susceptible to BitForge attacks.
- One of the key vulnerabilities identified in the BitForge series is tracked as CVE-2023-33241. This vulnerability affects the GG18 and GG20 threshold signature schemes (TSS), which are crucial for secure MPC wallet implementations. The vulnerability stems from a lack of proper checking on the attacker's Paillier modulus (N) and the encryption status based on factors or biprimes. Exploiting this flaw could allow an attacker to obtain private key shards and eventually the master secret key.
- The Lindell17 2PC protocol vulnerability (CVE-2023-33242) follows a similar pattern. This vulnerability enables attackers to extract the entire private key through a mishandling of aborts in the wallet's signing operations. This can occur in either an asymmetric attack by corrupting the client or server. In both scenarios, a series of specially crafted messages or commands can expose parts of the private key, which can then be used to reconstruct the entire secret key.
The severity of these vulnerabilities depends on multiple factors, such as the specific implementation parameters and the resources available to the attacker. Researchers have provided detailed proof-of-concept (PoC) exploits for each of the vulnerabilities. With the vulnerabilities having a PoC, it becomes much more probable that they will be exploited since an attacker can reverse engineer it and work out a malicious implementation.
