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

pytest: test for parallel bookkeeper queries.

Public commit record

What the developer wrote

Authored by Rusty Russell

70/100 · Adequate
pytest: test for parallel bookkeeper queries.

If both refresh new events, we will get an assertion:

```
```

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
✓ 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 only adds a new test case for the bookkeeper plugin. The test runs two list-income queries at the same time and is currently marked as expected to fail (xfail), meaning the underlying crash or assertion failure it checks for has not been fixed yet. The commit itself does not change any production code, so it cannot directly fix a vulnerability.

Recommended action

Treat this as a bug report / reproducer, not a security fix. Investigate the bookkeeper plugin's shared state and event-refresh logic for race conditions, and fix the assertion before removing xfail. Review whether the crash is reachable by normal RPC users and whether it could be abused for denial of service.

Security signals we found

01

Concurrency/crash condition in bookkeeper plugin (documented by test only)

02

Assertion failure when parallel queries both refresh new events (described in commit message)

03

No production code patch present

Risk score

Why this scored 29/100

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