37 matches found
CVE-2021-41593
Lightning Labs lnd before 0.13.3-beta allows loss of funds because of dust HTLC exposure...
Cross site request forgery (csrf)
Lightning Labs lnd before 0.13.3-beta allows loss of funds because of dust HTLC exposure...
CVE-2021-41593
Lightning Labs lnd before 0.13.3-beta allows loss of funds because of dust HTLC exposure...
CVE-2021-41593
CVE-2021-41593 affects Lightning Labs lnd prior to 0.13.3-beta. The issue is described as a dust HTLC exposure that can lead to loss of funds. Root cause and impact are noted in multiple connected sources; the affected component is lnd (Lightning Network daemon). Remediation is to upgrade to v0.1...
Lightning Labs Lnd 安全漏洞
Lightning Labs Lnd is a Lightning Network daemon. Lightning Labs lnd has a security vulnerability, there is no information about this vulnerability at this time, please stay tuned to CNNVD or vendor announcements...
CVE-2020-26895
Prior to 0.10.0-beta, LND Lightning Network Daemon would have accepted a counterparty high-S signature and broadcast tx-relay invalid local commitment/HTLC transactions. This can be exploited by any peer with an open channel regardless of the victim situation e.g., routing node, payment-receiver,...
CVE-2020-26895
Prior to 0.10.0-beta, LND Lightning Network Daemon would have accepted a counterparty high-S signature and broadcast tx-relay invalid local commitment/HTLC transactions. This can be exploited by any peer with an open channel regardless of the victim situation e.g., routing node, payment-receiver,...
CVE-2020-26896
Prior to 0.11.0-beta, LND Lightning Network Daemon had a vulnerability in its invoice database. While claiming on-chain a received HTLC output, it didn't verify that the corresponding outgoing off-chain HTLC was already settled before releasing the preimage. In the case of a hash-and-amount...
Design/Logic Flaw
Prior to 0.11.0-beta, LND Lightning Network Daemon had a vulnerability in its invoice database. While claiming on-chain a received HTLC output, it didn't verify that the corresponding outgoing off-chain HTLC was already settled before releasing the preimage. In the case of a hash-and-amount...
Open redirect
Prior to 0.10.0-beta, LND Lightning Network Daemon would have accepted a counterparty high-S signature and broadcast tx-relay invalid local commitment/HTLC transactions. This can be exploited by any peer with an open channel regardless of the victim situation e.g., routing node, payment-receiver,...
CVE-2020-26896
Prior to 0.11.0-beta, LND Lightning Network Daemon had a vulnerability in its invoice database. While claiming on-chain a received HTLC output, it didn't verify that the corresponding outgoing off-chain HTLC was already settled before releasing the preimage. In the case of a hash-and-amount...
CVE-2020-26896
The CVE affects LND (Lightning Network Daemon) prior to version 0.11.0-beta, specifically its invoice database. The root cause is that, when claiming an on-chain HTLC output, LND did not verify that the corresponding off-chain HTLC had already been settled before releasing the preimage. In a hash...
CVE-2020-26895
CVE-2020-26895 affects LND versions prior to 0.10.0-beta. The root cause is the handling of a counterparty high-S signature which could lead to the broadcast of invalid local commitment/HTLC transactions. This allows any peer with an open channel—whether routing node, payment-sender, or payment-r...
CVE-2020-26895
Prior to 0.10.0-beta, LND Lightning Network Daemon would have accepted a counterparty high-S signature and broadcast tx-relay invalid local commitment/HTLC transactions. This can be exploited by any peer with an open channel regardless of the victim situation e.g., routing node, payment-receiver,...
CVE-2019-12999
Lightning Network Daemon lnd before 0.7 allows attackers to trigger loss of funds because of Incorrect Access Control...
CVE-2019-12999
Lightning Network Daemon lnd before 0.7 allows attackers to trigger loss of funds because of Incorrect Access Control...
CVE-2019-12999
The CVE-2019-12999 issue affects the Lightning Network Daemon (lnd) up to version 0.7 (pre-0.7). The root cause is Incorrect/ Improper Access Control, enabling attackers to trigger loss of funds. Public document sets (GHSA-78HJ-86CR-6J2V and OSV entries) corroborate an access-control weakness in ...