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

libwalletqt: fix potential out-of-bounds read

Public commit record

What the developer wrote

Authored by tobtoht

45/100 · Thin
libwalletqt: fix potential out-of-bounds read
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes a bug in Feather Wallet's transaction handling code where reading a fee or mixin value could access memory outside the intended list if the list was empty. The old check used unsigned arithmetic that could wrap around when empty, making the guard ineffective. The new check explicitly handles empty lists and uses a safer comparison. This could have caused crashes or incorrect transaction data being read.

Recommended action

Review whether these functions are reachable from user-controlled input paths (e.g., transaction parsing or UI display), and consider adding regression tests for empty transaction vectors. The fix should be included in the next release.

Security signals we found

01

Out-of-bounds read due to unsigned integer underflow in bounds check

02

Undefined behavior on empty std::vector access

03

Fix present in commit title and diff

Risk score

Why this scored 44/100

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