GHSA-3fv3-hhmm-4x2q: Gitea user and organization feed token scope bypass
The /{username} web route accepted personal access tokens over HTTP Basic authentication without checking their scope. A token confined to an unrelated scope, such as read:issue, could read its owner's private activity through the user RSS/Atom feed and the profile activity tab, and other members' activity in a private organization through the organization feed; a public-only token could list the owner's private repositories and organizations and render private profile READMEs. For a site administrator's token this applied to every account. Tokens are now accepted on this route only for feeds, which require read:user or read:organization.
Event History
Frequently Asked Questions
Which tokens could expose private data?
Personal access tokens accepted through HTTP Basic authentication on the /{username} route were affected even when their scopes did not authorize the accessed data. This included tokens limited to unrelated scopes such as read:issue and public-only tokens.
What private information could be disclosed?
An affected token could read its owner's private activity through the user RSS/Atom feed and profile activity tab. It could also expose private repositories, organizations, and profile READMEs; organization feeds could reveal other members' activity in a private organization.
Does the impact increase for administrator tokens?
Yes. When the token belonged to a site administrator, the scope bypass applied to every account.
What access is required after the change?
Tokens are accepted on this route only for feeds. User feeds require read:user, and organization feeds require read:organization.