Gitea
Gitea push mirror SSRF and forced writes to internal Git hosts
Gitea validated a push mirror's remote address against the `[migrations]` allow and block lists only when the mirror was created. Each synchronization passed the stored address directly to `git push`, so a name that later resolved to a blocked or internal address was still reached. A user with administrator access to a repository, which includes repositories they create themselves, could aim push mirror synchronization at internal Git services and force-push the repository's contents to them.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.1high · scored by CISA ADP · CWE-367
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/39010
- Patch github.com/go-gitea/gitea/pull/39426
2 more
- Release notes blog.gitea.com/release-of-28.0.0
- 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.