CVE-2023-7346: Ledger Bitcoin App 2.1.0 Address Derivation Error via Miniscript
Ledger Bitcoin app versions 2.1.0 and 2.1.1 contain an address derivation vulnerability that allows attackers to cause incorrect Bitcoin addresses to be displayed by exploiting improper handling of miniscript policies containing the a: fragment. Attackers can craft malicious miniscript policies that cause the device to derive and display incorrect receiving addresses, potentially leading to funds being sent to unintended addresses.
Security readout for executives and security teams
Plain-English summary
CVE-2023-7346 is a Ledger Bitcoin app flaw where certain Miniscript wallet policies can make a device show the wrong receiving address. If a user trusts that displayed address, Bitcoin could be sent to an unintended address. The issue requires a crafted policy and user action; no active exploitation is reported in the provided sources.
Executive priority
Prioritize if the organization uses Ledger devices for Bitcoin custody with Miniscript workflows. The main business risk is misdirected funds, not system compromise. For standard users without Miniscript policy use, urgency appears lower but version verification is still warranted.
Technical view
The flaw is an address-derivation error in Ledger Bitcoin app handling of Miniscript policies containing the “a:” fragment. The CVSS 4.0 score is 4.1, with physical attack vector, high complexity, required attack conditions, and active user interaction. The listed weakness is CWE-682, incorrect calculation.
Likely exposure
Exposure appears limited to users or organizations using Ledger Bitcoin app versions identified in the advisories and Miniscript-based policies. The bundle mentions versions 2.1.0 and 2.1.1 in the description, but also lists 2.1.2 as affected, so confirm against Ledger’s bulletin.
Exploitation context
An attacker would need to introduce or influence a malicious Miniscript policy and get the user to rely on the resulting displayed receive address. This is not described as remote mass exploitation, and the CVE is not listed as KEV in the provided data.
Researcher notes
The provided metadata contains a version inconsistency: the narrative names 2.1.0 and 2.1.1, while the affected list also includes 2.1.2. Do not assume exploit availability or a fixed version from this bundle alone; use Ledger’s advisory as the primary source.
Mitigation direction
Check Ledger Security Bulletin 019 for the authoritative fixed or safe app version.
Update the Ledger Bitcoin app when Ledger guidance identifies a corrected release.
Avoid using untrusted Miniscript policies with affected Ledger Bitcoin app versions.
Treat unexpected receive addresses as suspicious and verify wallet policy provenance.
Validation and detection
Inventory Ledger devices using the Bitcoin app and record app versions.
Identify workflows using Miniscript policies, especially externally supplied policies.
Compare installed versions against Ledger Security Bulletin 019 and CVE records.
Review recent receiving-address generation events for policy source and user approval context.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-682: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-682 · source CWE mapping
Incorrect Calculation
Incorrect Calculation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.