Gitea
Gitea public-only token bypass in repository and organization creation
Gitea 1.27.3 stopped personal access tokens restricted to public resources (`public-only`) from creating repositories through `POST /api/v1/user/repos` and `POST /api/v1/repos/migrate`, but `POST /api/v1/org/{org}/repos`, `POST /api/v1/orgs/{org}/repos`, `POST /api/v1/orgs` and `POST /api/v1/repos/{owner}/{repo}/generate` still accepted such tokens. A holder of a public-only token with the needed write scopes could create private repositories in organizations where the token's owner may create repositories, create private organizations, and generate private repositories from templates. The token still could not read the private repositories it created.
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/39690
- Patch github.com/go-gitea/gitea/pull/39853
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.