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

Fix: When a server has too many apps, the Policies page timeout or crash (#7406)

Public commit record

What the developer wrote

Authored by Nicolas Dorier

70/100 · Adequate
Fix: When a server has too many apps, the Policies page timeout or crash (#7406)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes a performance problem on the BTCPay Server 'Policies' settings page. Previously, the page tried to load a dropdown list of every app on the server, which could time out or crash when there were many apps. The fix replaces the dropdown with a simple text box where the administrator types an app ID directly. It also adds validation to reject invalid app IDs instead of crashing. The change is primarily a reliability/performance fix, but it slightly changes how app IDs are entered and validated.

Recommended action

Review the new text-input flow for usability and ensure the server-side validation covers all paths where AppId is submitted. Consider whether rate limiting or additional authorization checks are needed now that the UI no longer restricts values to existing apps. No urgent security patch appears required, but administrators should verify that only authorized users can access the Server Policies page.

Security signals we found

01

Change from bounded select list to free-form text input for app identifiers

02

Added server-side validation (TryGetValue + ModelState.AddModelError) for RootAppId and DomainToAppMapping AppId values

03

Removed potentially expensive server-side query that loaded all apps into view state

04

Fixes a denial-of-service-like symptom (page timeout/crash) for servers with many apps

Risk score

Why this scored 37/100

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