The Gitea API endpoint `GET /api/v1/repos/{owner}/{repo}/media/{filepath}` wrote files of up to 1 KiB that are stored directly in Git, not in LFS, to the response without the content type and disposition headers Gitea uses for user content. An HTML file committed to a repository was therefore rendered by the browser on the Gitea origin. A user who can push to a repository could run JavaScript in the session of a victim who opens the media URL and act with the victim's permissions.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
None
No privileges needed
User Interaction
Required
User action required
Impact Assessment
Confidentiality
Low
Partial data leak
Integrity
Low
Partial data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Gitea Gitea
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
|
— |
28.1.0
|
References 5
https://github.com/go-gitea/gitea/security/advisories/GHSA-94rx-fqm6-q23v
GitHub Security Advisory GHSA-94rx-fqm6-q23v
https://github.com/go-gitea/gitea/pull/39501
Fix: go-gitea/gitea pull request #39501
https://github.com/go-gitea/gitea/pull/39507
Fix backport to release/v28: go-gitea/gitea pull request #39507
https://blog.gitea.com/release-of-28.1.0/
Gitea 28.1.0 release announcement
https://github.com/go-gitea/gitea/releases/tag/v28.1.0
go-gitea/gitea v28.1.0 release