Horizon Alert
Summary of the vulnerability and why it matters
This advisory concerns a vulnerability in the Nostr Wallet Connect plugin for the Electrum Bitcoin wallet. The issue allows malicious wallet connections to bypass daily spending limits, potentially leading to unauthorized fund withdrawals. The primary concern is to confirm if this specific plugin is in use within your organization.
- A plugin flaw can bypass spending limits.
- Consider if this specific plugin is used.
- Confirm relevance and exposure to potential risks.
Attack Path
How an attacker could exploit the issue
An attacker could exploit this vulnerability by sending specially crafted payment requests to a vulnerable Electrum wallet. This could be achieved by interacting with the Nostr Wallet Connect plugin, which does not properly validate spending limits. Successfully exploiting this could allow an attacker to drain funds beyond the intended daily limit.
- No special access required.
- Concurrent, truncated payment requests.
- Unauthorized fund withdrawal.
Live Threat
Current exploitation, exposure, and threat context
This vulnerability in the Nostr Wallet Connect plugin for Electrum could allow a malicious client to bypass configured daily spending limits. This occurs when concurrent payment requests are made, or when very small amounts are repeatedly sent, potentially leading to unauthorized fund expenditure beyond the set limit.
- User's cryptocurrency funds could be at risk.
- Malicious NWC clients could exploit budget checks.
- Funds could be drained beyond the daily limit.
Operational Fix
Recommended remediation, mitigation, and detection steps
The Electrum wallet's Nostr Wallet Connect plugin is affected by a spending limit bypass vulnerability. This issue requires application owners and platform teams to identify instances of Electrum, determine their exposure, and plan remediation. The initial step involves locating all deployments, verifying business criticality and reachability, and assigning ownership for the response.
- Application owners should address this.
- Verify usage and identify affected instances.
- Coordinate vendor fixes and schedule updates.