Skip to content

server/v2auth: reject empty permission patterns - #22379

Open
Pyolar wants to merge 1 commit into
etcd-io:release-3.5from
Pyolar:fix/v2auth-empty-permission-pattern
Open

server/v2auth: reject empty permission patterns#22379
Pyolar wants to merge 1 commit into
etcd-io:release-3.5from
Pyolar:fix/v2auth-empty-permission-pattern

Conversation

@Pyolar

@Pyolar Pyolar commented Sep 4, 2026

Copy link
Copy Markdown

simpleMatch and prefixMatch in the v2 auth package dereference pattern[len(pattern)-1] without checking whether the pattern is empty. An empty-string permission pattern can be stored through the v2 role API (no validation when the role is created or updated), and the next time a user whose role carries that pattern accesses a key, matching panics with runtime error: index out of range [-1]. The panic is recovered by net/http which then closes the connection, so the request is dropped without a response.

Fix

Treat an empty pattern as non-matching in both simpleMatch and prefixMatch so that roles containing an empty pattern are denied access gracefully instead of crashing the request handler.

Test

Added TestEmptyPatternDoesNotPanic covering HasKeyAccess, HasRecursiveAccess, simpleMatch and prefixMatch with an empty pattern, plus a sanity check that the * wildcard still matches.

simpleMatch and prefixMatch dereference pattern[len(pattern)-1] without
checking whether the pattern is empty. An empty-string permission pattern
can be stored through the v2 role API, and matching it then panics with
"runtime error: index out of range [-1]", which drops the client request.

Treat an empty pattern as non-matching so that a role carrying one is
denied access gracefully instead of crashing the request handler.

Signed-off-by: sunliqiang <sunliqiang@kylinos.cn>
@kubernetes-prow

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Pyolar
Once this PR has been reviewed and has the lgtm label, please assign ahrtr for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubernetes-prow

Copy link
Copy Markdown

Hi @Pyolar. Thanks for your PR.

I'm waiting for a etcd-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant