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

askrene: handle maxparts parameter values 1 and 0.

Public commit record

What the developer wrote

Authored by Rusty Russell

65/100 · Adequate
askrene: handle maxparts parameter values 1 and 0.

For 1, we use single-path. For 0, reject.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
The short version

What changed, and why it matters

This commit fixes how the askrene routing plugin handles the maxparts parameter. Previously, setting maxparts to 1 did not force single-path routing, and setting it to 0 was accepted even though it makes no sense. Now, maxparts=1 forces single-path routing, and maxparts=0 is rejected with an error. This is a minor correctness and input-validation improvement, not a critical security fix.

Recommended action

No urgent action required. Treat as routine bug fix. Users and node operators should update as part of normal maintenance. No evidence of exploitable vulnerability.

Security signals we found

01

Input validation added for maxparts == 0

02

Algorithm selection corrected for maxparts == 1

03

Defensive consistency fix in routing plugin

Risk score

Why this scored 28/100

Our methodology →
Potential impact 5/30
Exploitability 3/25
Stealth signal 4/15
Affected reach 5/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.