BitcoinBTC, coin
DevelopingSecurity

Unpatched Eclair Lightning nodes could crash again on every restart

CryptoSlate reported that an unpatched Eclair flaw lets a peer crash Bitcoin Lightning nodes on every restart without spending BTC on-chain; v0.14.1 fixed it in July.

Why it matters

A peer could take a node down without committing BTC to an on-chain transaction, and the saved channel records keep it down across restarts. CryptoSlate reported the fix shipped in July while the disclosures came at the end of September, so nodes on v0.14.0 or earlier stayed exposed through that gap; the article gave no count of affected operators.

Key facts

Eclair, a Bitcoin Lightning implementation, had a flaw that could crash reachable nodes running v0.14.0 and earlier without an attacker spending BTC on-chain.

Reported by CryptoSlate

Inconsistent checks of temporary and final channel identifiers let Eclair's pending-channel counter undercount unfunded channels.

Reported by CryptoSlate

A malicious peer could accumulate saved channel requests without broadcasting the funding transaction or paying an on-chain fee.

Reported by CryptoSlate

Saved channel records could exhaust memory again on restart, so restarting the node was not enough to restore service.

Reported by CryptoSlate

Researcher Erick Cestari published the persistent-crash finding on Sept. 30.

Reported by CryptoSlate

Cestari explained the persistent-crash finding alongside a separate denial-of-service bug in a developer post on Oct. 1.

Reported by CryptoSlate

Both flaws were fixed in Eclair v0.14.1, released in July before the public disclosures.

Reported by CryptoSlate

ACINQ recommends the later v0.14.3 security release, which CryptoSlate said addresses separate vulnerabilities.

Reported by CryptoSlate

What happened

CryptoSlate reported that Eclair, a Bitcoin Lightning implementation, contains a flaw that lets a malicious peer crash reachable nodes without spending BTC on-chain, affecting nodes running v0.14.0 and earlier. The cause, according to the outlet, is inconsistent checks of temporary and final channel identifiers, which let Eclair's counter undercount unfunded channels so a peer could pile up saved requests without broadcasting a funding transaction or paying an on-chain fee. Researcher Erick Cestari published the persistent-crash finding on Sept. 30 and set out the same flaw alongside a separate denial-of-service bug in an Oct. 1 developer post. CryptoSlate reported that both flaws were fixed in v0.14.1, released in July before the public disclosures, and that saved channel records can exhaust memory again on restart, so a restart does not restore service. The outlet also reported that ACINQ now recommends the later v0.14.3 security release for separate vulnerabilities. CryptoSlate did not say how many nodes were exposed or whether any have been crashed in the wild, and the article text ends mid-sentence while describing what the attack required beyond computing power.

How the story developed

  1. Update

    Erick Cestari publishes the persistent-crash finding

    The researcher disclosed that an unfunded-channel flaw could crash Eclair nodes and that saved channel records made restart insufficient.

    CryptoSlate

  2. Official statement

    Cestari details the flaw and a separate denial-of-service bug in a developer post

    The Oct. 1 post set out both issues, including inconsistent checks of temporary and final channel identifiers.

    CryptoSlate

  3. First report

    First report by CryptoSlate

    Unpatched Eclair Bitcoin Lightning nodes could crash again every time they restart

    CryptoSlate

  4. Resolution

    Eclair v0.14.1 released with fixes for both disclosed flaws

    The July release fixed the persistent-crash flaw and a separate denial-of-service bug before either was made public.

    CryptoSlate

  5. Update

    ACINQ recommends the later v0.14.3 security release

    CryptoSlate reported ACINQ now points operators to v0.14.3 for separate vulnerabilities.

    CryptoSlate

  6. Update

    CryptoSlate reports the unpatched-node crash risk

    The outlet said reachable nodes on v0.14.0 and earlier could be crashed repeatedly on restart without on-chain BTC expenditure.

    CryptoSlate

Affected entities

Original sources

PublisherReportRolePublished
CryptoSlate
Crypto media
Unpatched Eclair Bitcoin Lightning nodes could crash again every time they restartOriginal