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

Merge pull request #10798 from SomberNight/202608_base43

Public commit record

What the developer wrote

Authored by Felix

73/100 · Adequate
Merge pull request #10798 from SomberNight/202608_base43

transaction: cap max tx size we allow for base43
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit fixes a performance weakness in Electrum's handling of large Bitcoin transactions encoded in 'base43'. The base43 encoding and decoding functions run in quadratic time, meaning the work grows much faster than the input size. An attacker could send or feed Electrum a very large base43 transaction string and cause the program to freeze or become unresponsive for a noticeable period (a denial-of-service effect). The patch limits how large a base43 string Electrum will try to decode and also makes the encoder slightly faster. It does not fix the underlying quadratic algorithm.

Recommended action

Treat this as a low-to-moderate denial-of-service hardening patch. Users and downstream packagers should apply it. For a stronger fix, replace the base43 implementation with a linear-time algorithm or avoid base43 for large payloads entirely, as the FIXME comments suggest.

Security signals we found

01

Quadratic-time base43 encode/decode can be triggered on attacker-controlled input

02

Denial-of-service via CPU exhaustion / UI freeze on large transaction strings

03

Input-length cap added as a defensive guard, not a full algorithmic fix

04

Developer comment explicitly calls out the quadratic complexity and the DoS risk

05

No cryptographic weakness or funds-theft vector is present in the diff

Risk score

Why this scored 51/100

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