Gitea
Gitea OAuth2 account auto-linking takeover through the sign-up form
When `[oauth2_client].ACCOUNT_LINKING` is set to `auto` (not the default) and registration is enabled, the link-account sign-up form looked up the existing account to link by the user name or email submitted in the form instead of the identity asserted by the OAuth2 provider. An attacker with an account on a configured OAuth2 provider could submit another user's name, link their external identity to that Gitea account and be signed in as it without its password, including as an administrator. The link persisted for later sign-ins. Automatic linking now only happens when the existing account matches the provider's email or provider-derived user name; otherwise the account password is required.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 28.3.0
Fixed in 28.3.0
Mitigation
Upgrade Gitea to 28.3.0 or later.
References
- Vendor advisory github.com/go-gitea/gitea/security/advisories/…
- Patch github.com/go-gitea/gitea/pull/40121
- Patch github.com/go-gitea/gitea/pull/40137
2 more
- Release notes blog.gitea.com/release-of-28.3.0
- Release notes github.com/go-gitea/gitea/releases/tag/v28.3.0
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.