Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

go-oauth2/oauth2
master @ c1329d9
10
Fixes
2
CVEs
CRITICAL
Peak severity
Highlights
Auth Bypass: 7 prior fixes. Scrutinize any change in this area.
manage/manager.go: most-fixed (4 issues). Treat as high-risk during review.
6 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Auth Bypass: Flawed conditional logic in client secret checks allowed authentication to be bypassed entirely when an empty secret string was supplied by a client. Developers must enforce strict, non-bypassable equality and cryptographic verification on all client credentials.
Auth Bypass: Missing client_id and incorrect PKCE code_verifier validations during token requests created opportunities for authorization code interception. Ensuring that client identifiers and PKCE code challenges are rigorously verified for authorization flow requests is vital.
Open Redirect: Failing to properly validate or fall back on client-registered domains when a redirection URI is left empty or arbitrary can lead to open redirection vulnerabilities. Redirection targets must always be validated against a strict domain whitelist.