جزئیات آسیب‌پذیری

خلاصه‌ی فارسی برای این آسیب‌پذیری هنوز تهیه نشده است.

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.

• https://github.com/go-gitea/gitea/security/advisories/GHSA-6h2f-c8jm-84hc vendor-advisory
• https://github.com/go-gitea/gitea/pull/39942 patch
• https://github.com/go-gitea/gitea/pull/40085 patch
• https://blog.gitea.com/release-of-28.3.0/ release-notes
• https://github.com/go-gitea/gitea/releases/tag/v28.3.0 release-notes