Skip to content

Do not allow wildcards in the hostname for Valid Redirect Address#48793

Open
rmartinc wants to merge 1 commit intokeycloak:mainfrom
rmartinc:issue-48430
Open

Do not allow wildcards in the hostname for Valid Redirect Address#48793
rmartinc wants to merge 1 commit intokeycloak:mainfrom
rmartinc:issue-48430

Conversation

@rmartinc
Copy link
Copy Markdown
Contributor

@rmartinc rmartinc commented May 7, 2026

Closes #48430

This PR avoid wildcards in the hostname. For backwards compatibility it manages https://test* as https://test/*. Maybe it's a bit confusing, so if you prefer to not modify the configured valid redirect URI and just reject (performing exact matching) for those kind of patterns just let me know. I have been hesitating between the two options all the time.

Closes keycloak#48430

Signed-off-by: rmartinc <rmartinc@redhat.com>
@rmartinc rmartinc requested a review from a team as a code owner May 7, 2026 12:40
@rmartinc
Copy link
Copy Markdown
Contributor Author

rmartinc commented May 7, 2026

@ahus1 @mposolda Take a look when you have time. It's the hardening issue about RedirectUtils. I decided to maintain backwards compatibility as much as I can, although it's a bit strange now.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Wildcard redirect URI matching does not enforce host boundary when * is placed directly after hostname

1 participant