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

askrene-getroutes: add test for source==destination

Public commit record

What the developer wrote

Authored by Lagrang3

75/100 · Adequate
askrene-getroutes: add test for source==destination

Changelog-None

Signed-off-by: Lagrang3 <lagrang3@protonmail.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit adds a test that checks Core Lightning's routing plugin (askrene) properly rejects a request where the payment source and destination are the same node. The test is marked as expected to fail for now, meaning the bug it checks for likely still exists in the code. If triggered, such a request could crash the lightning daemon instead of returning a clean error.

Recommended action

Treat this as a low-severity bug report rather than an active vulnerability. The maintainer should implement input validation in `getroutes` to reject `source == destination` with the documented RPC error, then remove the `xfail` marker. Users should avoid passing identical source and destination nodes to `getroutes` until the fix lands.

Security signals we found

01

Potential denial-of-service via malformed RPC input (source==destination)

02

Test marked xfail indicates unpatched behavior

03

Crash of lightningd suggested by test docstring

Risk score

Why this scored 34/100

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