auth: Patreon provider assigns the same local user ID to every authenticated Patreon account, enabling cross‑user impersonation
go-pkgz auth
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/go-pkgz/auth Go |
|
|
| github.com/go-pkgz/auth/v2 Go |
|
|
go-pkgz auth
| Product | Affected | Fixed in |
|---|---|---|
| github.com/go-pkgz/auth Go |
|
|
| github.com/go-pkgz/auth/v2 Go |
|
|
auth provides authentication via oauth2, direct and email. From versions 1.18.0 to before 1.25.2 and 2.0.0 to before 2.1.2, the Patreon OAuth provider maps every authenticated Patreon account to the same local user.ID, instead of deriving a unique ID from the Patreon account returned by Patreon. In practice, this means all Patreon-authenticated users of an application using this library are collapsed into a single local identity. Any application that trusts token.User.ID as the stable account key can end up mixing or fully merging unrelated Patreon users, which can lead to cross-account access, privilege confusion, and subscription-state leakage. This issue has been patched in versions 1.25.2 and 2.1.2.
From the CVE record · GitHub_M
The Patreon OAuth provider maps every authenticated Patreon account to the same local user ID. In applications that use token.User.ID as a stable account key, an authenticated Patreon user may gain access to another user's account or subscription state. Exploitation requires Patreon authentication; no other user interaction is described.
Check applications using github.com/go-pkgz/auth versions >=1.18.0 <1.25.2 or github.com/go-pkgz/auth/v2 versions >=2.0.0 <2.1.2 with Patreon OAuth.