Scoped Admin Channel Registration Target Authorization Bypass

Vulnerability Overview This vulnerability involves the channel registration approval process within permission management. Specifically, a scoped admin can connect an unknown channel to an agent group they do not have permission to manage, thereby bypassing permission restrictions. Impact Scope Scoped Admins: Can connect unknown channels to agent groups they are not authorized to manage. Messaging: May lead to unauthorized message passing between channels and agent groups. Permission Boundaries: Breaks down the permission boundaries of scoped admins, allowing them to perform actions beyond their authorized scope. Remediation Plan 1. Approval Option Filtering: Filter channel registration approval options based on the approver's identity. 2. Target Group Selection Restriction: Display target group selection options only within groups where the approver has administrator permissions. 3. Response Handling Check: Re-validate target group authorization before applying pending channel registrations. 4. Regression Testing: Ensure that scoped admins cannot connect channels to other groups by selecting or submitting targets outside their scope. Patched Code Before and After Fix Comparison Before Fix: - Approval options were based on the reference group selection. - Initial and follow-up approval cards were constructed by all agent groups. - The final response checked whether the clicker could approve the pending row but did not verify if the same clicker could manage the selected target group. - Stale, hidden, or tampered response values could still reference target groups outside the scope. After Fix: - Approval options are filtered by the approver's identity. - Agent selection follow-up cards only include groups where the approver has administrator permissions. - The response handler rejects if the approver is not authorized for that target group. - Unauthorized attempts leave the approval pending and do not create a channel-to-agent-group connection. Attack Flow 1. A scoped admin has administrator permissions for Agent Group A but not for Agent Group B. 2. An unknown message channel triggers the channel registration approval process, using Group A as the approval context. 3. The scoped admin receives the approval card. 4. The approval follow-up or callback value submits . 5. In the vulnerable code, the handler accepts the target and creates a channel connection to Agent Group B. 6. After the fix, B is not included in the selectable options, and forged or stale values are rejected before connection creation. Affected Code Root Cause Pending approval authorization and target authorization were treated as the same decision. The approval row stored the reference group used to select the approver, but subsequent responses could choose a different target group. Option generation did not consider the approver's identity. The final application step did not re-check administrator permissions for the selected target group. CVSS Evaluation Issue: Scoped admin channel registration target authorization bypass CVSS v3.1: 6.4 Medium Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N Security Verification Steps 1. Create two agent groups, ag-1 and ag-2. 2. Grant administrator permissions only for ag-1. 3. Trigger the unknown channel registration process. 4. Process the approval as . 5. Verify that follow-up options include but do not include . 6. Submit a forged/stale response value. 7. Verify that no row is created and the pending approval remains pending. Expected Vulnerable Behavior In the vulnerable code, the final response is accepted even if the approver only manages ag-1. This creates a channel connection to agent group B, leading to unauthorized messaging. Changes in this PR Add approver-aware filtering for channel registration option generation. Pass the actual user delivering the approval to the initial card builder. Pass the approver ID to the agent selection follow-up builder. Add an application-time authorization check before applying . Add regression test coverage for scoped admin cross-group target cases. File Changes Maintainer Impact This PR is a narrow authorization fix. It does not change owner/global admin flows, pending approval patterns, or general unknown channel registration behavior. It restricts target selection to the approver's existing authorizations and rejects target values that do not match the scope. Reason for Fix The approval process involves two separate security decisions: 1. Whether the clicker is allowed to respond to the pending approval; 2. Whether the selected target agent group is within the clicker's management scope. Both checks must be enforced. Filtering options improves the normal UI path, while the response handler check protects server-side boundaries against stale cards, hidden options, or direct callbacks/value submissions. Change Type Security fix Regression tests Test Plan Local run commands: Final verification passed after formatting affected files. The focused channel regi

Goal Reached Thanks to every supporter — we hit 100%!

Scoped Admin Channel Registration Target Authorization Bypass

More from this source