AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
High 84 Bitcoin

Eclair v0.14.4 release (#3403)

Public commit record

What the developer wrote

Authored by Fabrice Drouin

53/100 · Thin
Eclair v0.14.4 release (#3403)

Eclair v0.14.4 release
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This commit is the official release marker for Eclair v0.14.4. The release notes included in the commit describe it as a security-hardening patch release with fixes for multiple issues, some of which can be exploited by malicious nodes. The most clearly described issue is a cross-site request forgery (CSRF) risk on the node's HTTP API: because the API uses HTTP basic authentication and accepts form-encoded parameters, any website visited by the node operator could trick the browser into making authenticated API calls. The release mitigates this by rejecting API requests that carry a browser-style Origin header. Other listed fixes cover seed-file validation, interactive transaction funding, remote closing scripts, channel funding/replacement logic, onion routing packet handling, and transaction publishing. The commit itself only changes version numbers, release notes, CI configuration, and build checksums; the actual code fixes are in the referenced parent commits.

Recommended action

Upgrade Eclair nodes to v0.14.4 promptly, as the vendor explicitly recommends upgrading and notes that some issues can be exploited by malicious nodes. Review any custom web front-ends that previously talked directly to the Eclair API and place a backend proxy in front, because direct browser access is now blocked by Origin-header rejection. Monitor the vendor's release notes and follow-up advisories for detailed per-issue guidance.

Security signals we found

01

Release notes explicitly label the release as containing 'security hardening fixes' exploitable by malicious nodes

02

HTTP API now rejects Origin-header requests to mitigate browser-based CSRF against basic-authenticated endpoints

03

Seed file length validation added (commit a07fff5)

04

Interactive-tx funding hardened against a malicious bitcoind (commit e43fbf6)

05

Remote closing script updates validated (commit 380feec)

06

Onion per-hop lengths exceeding packet size are rejected (commit d3a146a)

07

Unpublishable splices rejected (commit af99418)

08

Startup safety guard removed, indicating prior development build was considered unsafe

Risk score

Why this scored 84/100

Our methodology →
Potential impact 25/30
Exploitability 20/25
Stealth signal 12/15
Affected reach 13/15
Confidence 9/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.