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

lightningd: make sure we don't send channel_updates for unasked for channels.

Public commit record

What the developer wrote

Authored by Rusty Russell

73/100 · Adequate
lightningd: make sure we don't send channel_updates for unasked for channels.

We can decide to send an HTLC down a preferred channel which leads to the same peer
as the one they asked for, but the spec is clear that you shouldn't send the "wrong"
channel_update in that case.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Changelog-Fixed: Protocol: when we send errors, we won't include a `channel_update` if we chose a different channel than the one they told us to.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit fixes a protocol compliance bug in Core Lightning. When a payment failed and the node sent back an error message, it could attach a 'channel_update' for a different channel than the one the sender had asked to use. The fix makes sure the attached update matches the requested channel, and omits it if not. This mainly prevents routing confusion and fingerprinting rather than direct theft of funds.

Recommended action

Apply the patch. Nodes should upgrade to avoid sending non-compliant channel_updates, which can leak routing information and confuse peers' pathfinding.

Security signals we found

01

Protocol compliance fix for BOLT 4 channel_update requirement

02

Prevents disclosure of channel_update for a channel the peer did not ask about

03

Avoids routing hint / alias leakage when redirecting to an equivalent channel

04

Could reduce fingerprinting of channel topology or routing preferences

Risk score

Why this scored 40/100

Our methodology →
Potential impact 8/30
Exploitability 6/25
Stealth signal 7/15
Affected reach 8/15
Confidence 7/10
Evidence quality 4/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.