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

Merge pull request #7795 from tumutech/fix-api-key-permission-usage-analysis

Public commit record

What the developer wrote

Authored by Nicolas Dorier

73/100 · Adequate
Merge pull request #7795 from tumutech/fix-api-key-permission-usage-analysis

Fix API key View Usage crash with multi-store permission usage
✓ 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 crash in BTCPay Server's admin page that shows how an API key has been used. The crash happened when an API key had permissions tied to more than one store. The fix also corrects how usage counts are recorded and displayed so store-specific permissions are counted separately instead of being lumped together. It is primarily a reliability/functional bug fix; there is no direct evidence it created or fixed a security vulnerability that an attacker could exploit.

Recommended action

Treat as a routine bug-fix merge. Reviewers may optionally verify that the new TryAggregateUsage matching logic cannot be confused by malformed permission strings, and confirm the upsert idempotency still behaves correctly under concurrency. No urgent security response is indicated by the diff alone.

Security signals we found

01

Fixes a UI crash in an administrative API-key usage page

02

Corrects aggregation of permission usage records when permissions are scoped to specific stores

03

Changes database upsert to persist full permission string including store scope

04

Adds backward-compatible parsing for legacy usage rows that stored only the policy

05

No authentication bypass, authorization bypass, injection, or secret disclosure visible in the diff

Risk score

Why this scored 24/100

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