Skip to content

status --check scopes should cap CSV length before splitting #2913

Description

@Widthdom

Summary

status --check=<scopes> parses a comma-separated scope list without bounding the raw value length or number of entries.

Evidence

QueryCommandRunner handles inline --check= values with AddStatusCheckScopes, which loops over rawScopes.Split(,, StringSplitOptions.RemoveEmptyEntries | StringSplitOptions.TrimEntries) and lowercases each entry before validating against the finite scope set.

Impact

Large --check= values can allocate and process many entries before the command reports unsupported scopes.

Expected

Reject overlarge scope lists before splitting, using a documented maximum length and entry count.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions