Gitea
Gitea protected file pattern bypass with quoted file names
The "Protected file patterns" setting of a branch protection rule was checked against file names as git prints them, and git quotes names that contain a double quote, a backslash or a control character. Such names never matched a pattern, so a user with write access could add or change files under a protected pattern by direct push or through a pull request merge, and could move a protected file out of the pattern's reach by renaming it. Where the patterns protect workflow files, this allowed adding a workflow that then ran on the repository's runners. Changed files are now listed unquoted, and a rename reports both the old and the new path.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 28.4.0
Fixed in 28.4.0
Mitigation
Upgrade Gitea to 28.4.0 or later.
References
- Vendor advisory github.com/go-gitea/gitea/security/advisories/…
- Patch github.com/go-gitea/gitea/pull/40362
- Release notes blog.gitea.com/release-of-28.4.0
1 more
- Release notes github.com/go-gitea/gitea/releases/tag/v28.4.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.