CyberRota Analysis
AI-GeneratedThe Gitea API endpoint for retrieving media files is vulnerable, allowing users with push access to repositories to serve files directly from Git without proper content type and disposition headers. This can lead to the execution of arbitrary JavaScript in the context of a victim's session when they access the media URL, potentially compromising their permissions. Organizations using Gitea, particularly those with collaborative repository access, should prioritize addressing this vulnerability to mitigate the risk of cross-site scripting (XSS) attacks.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
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.
Related CVEs
Other vulnerabilities affecting the same vendor(s)