Gitea archived repository release, milestone and label modification
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Gitea 28.3.0.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Gitea | Gitea | <28.3.0 | 28.3.0 |
Exploit evidence
1 public sources
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Gitea, strongest first
Embed
A live severity badge for an advisory, README or ticket