Gitea archived repository modification via release and metadata APIs
Gitea
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Gitea Gitea |
| No fix yet |
Original description
The API routes for releases, release assets, milestones and repository labels did not reject changes to archived repositories. A user with write access to an archived repository, or a holder of such a user's write-scoped token, could replace or delete release assets while keeping their download URLs, delete releases and tags, and create, edit or delete milestones and labels of a repository that is meant to be read-only. Changing requests on these routes now return 423 Locked for archived repositories.
From the CVE record · Gitea