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

Respect rejected API key permissions (#7744)

Public commit record

What the developer wrote

Authored by Nicolas Dorier

53/100 · Thin
Respect rejected API key permissions (#7744)
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes a bug in BTCPay Server's API key authorization flow. When a user was asked to approve a set of permissions for an app, unchecking (rejecting) certain permissions was being ignored. As a result, the issued API key could end up with permissions the user explicitly rejected. The fix ensures rejected permissions are not granted and that the system correctly asks again later if an app requests a previously rejected permission.

Recommended action

Review and deploy this patch. Verify that non-strict OAuth-style authorization flows correctly honor user rejections and that re-authorization prompts for newly requested permissions. Audit any API keys issued before this patch to confirm they match the permissions users actually consented to.

Security signals we found

01

Authorization bypass: user rejection of API key permissions was not honored

02

Privilege escalation via over-permissive API key issuance

03

UI consent state not correctly propagated to stored permissions

04

Null reference risk in existing key matching logic

05

Regression test added for selective permission rejection

Risk score

Why this scored 62/100

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