Gitea
Gitea deploy key pushes acting as the repository owner
When a push was authenticated with a deploy key, Gitea recorded the repository owner as the pusher, so permission checks in the push hook pipeline evaluated the owner instead of the deploy key. A holder of a writable deploy key could create protected tags without being on the tag allow list and change repository visibility through push options, for example making a private repository public. Pull requests created through the AGit flow with a deploy key were also attributed to the owner.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.1high · scored by CISA ADP · CWE-863
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Gitea Gitea
- <= 1.27.3
Mitigation
The record names no fix. Check the vendor advisory below.
References
- Vendor advisory github.com/go-gitea/gitea/security/advisories/…
- Patch github.com/go-gitea/gitea/pull/37306
- Release notes blog.gitea.com/release-of-28.0.0
1 more
- Release notes github.com/go-gitea/gitea/releases/tag/v28.0.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.