vulnerability / NVI-00020082 / Revision 1
Gitea: OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes
GitHub lists this reviewed advisory for code.gitea.io/gitea. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
code.gitea.io/gitea
source listed< 1.27.0
### Summary The OIDC userinfo endpoint (`GET /login/oauth/userinfo`) accepts Gitea API tokens as bearer credentials but does not enforce API token scopes before returning identity claims. A personal access token scoped only to `read:misc` can successfully retrieve user information from the OIDC userinfo endpoint, even though the same token is denied access to user-related REST API endpoints that enforce scope checks. As a result, identity information remains accessible through the OIDC endpoint regardless of the scopes assigned to the API token. ### Details Gitea supports scoped personal access tokens and enforces scope checks on user-related REST API endpoints. For example, a token scoped only to `read:misc` is denied access to endpoints such as: | Endpoint | Required Scope | |----------|----------------| | `GET /api/v1/user` | `read:user` | | `GET /api/v1/user/emails` | `read:user` | | `GET /api/v1/user/orgs` | `read:organization` | Requests to these endpoints return: ```http 403 Forbidden ``` with a scope-related error. However, the same `read:misc` token can be supplied as a bearer credential to: ```http GET /login/oauth/userinfo Authorization: Bearer ``` a
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-mg4f-x9v4-6h2p ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.