Phishing: Attackers can use trusted domain links to redirect victims to credential-harvesting pages OAuth/SSO Token Theft: In authentication flows, authorization codes or tokens may leak via redirect Referer Leakage: Sensitive URL parameters may be exposed to attacker domains via the Referer header Cache Poisoning: In deployments with shared caches, malicious redirects may be cached and served to other users
Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository names through previously started stopwatches.
Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private repository is revoked, they may still view issue and pull request titles through previously received notifications.
Gitea does not properly verify authorization when canceling scheduled auto-merges via the web interface. A user with read access to pull requests may be able to cancel auto-merges scheduled by other users.
Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could potentially be linked to a release in a different public repository, making it accessible to unauthorized users.
Gitea does not properly validate repository ownership when deleting Git LFS locks. A user with write access to one repository may be able to delete LFS locks belonging to other repositories.
Gitea does not properly validate project ownership in organization project operations. A user with project write access in one organization may be able to modify projects belonging to a different organization.
Gitea does not properly validate ownership when toggling OpenID URI visibility. An authenticated user may be able to change the visibility settings of other users' OpenID identities.
In Gitea through 1.17.1, repo cloning can occur in the migration function.
Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4.
In Jenkins Gitea Plugin 1.4.4 and earlier, the implementation of Gitea personal access tokens does not support credentials masking, potentially exposing them through the build log.
Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.
In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to private issue titles.
Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9.
Gitea before 1.16.7 does not escape git fetch remote.
An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file.
Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5.
The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL.
Improper Authorization in GitHub repository go-gitea/gitea prior to 1.16.4.
models/repo_mirror.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 mishandles mirror repo URL settings, leading to remote code execution.
repo/setting.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 does not validate the form.MirrorAddress before calling SaveAddress.
Gitea version prior to version 1.5.1 contains a CWE-200 vulnerability that can result in Exposure of users private email addresses. This attack appear to be exploitable via Watch a repository to receive email notifications. Emails received contain the other recipients even if they have the email set as private. This vulnerability appears to have been fixed in 1.5.1.
An issue exsits in Gitea, which could let a malicious user gain privileges due to client side cookies not being deleted and the session remains valid on the server side for reuse.
An Authentication Bypass vulnerability exists in Gitea, which could let a malicious user gain privileges. If captured, the TOTP code for the 2FA can be submitted correctly more than once.
Gitea is affected by URL Redirection to Untrusted Site ('Open Redirect') via internal URLs.
Server Side Request Forgery (SSRF) vulneraility exists in Gitea using the OpenID URL.
Cross Site Scripting (XSS) vulnerability exists in Gitea via the repository settings inside the external wiki/issue tracker URL field.
Cross Site Request Forgery (CSRF) vulnerability exists in Gitea via API routes.This can be dangerous especially with state altering POST requests.
Gitea which could let a remote malisious user execute arbitrary code.
Gitea allows XSS via certain issue data in some situations.
Stack buffer overflow vulnerability in gitea allows remote attackers to cause a denial of service (crash) via vectors related to a file path.
Gitea does not prevent a git protocol path that specifies a TCP port number and also contains newlines (with URL encoding) in ParseRemoteAddr in modules/auth/repo_form.go.
The git hook feature in Gitea allows for authenticated remote code execution.
In Gitea, an attacker can trigger a deadlock by initiating a transfer of a repository's ownership from one organization to another.
Gitea is affected by a Cross Site Scripting vulnerability. An attacker may be able execute arbitrary JS in a victim's browser.
Gitea is affected by a Cross Site Scripting (XSS) vulnerability. an attacker may be able to execute arbitrary JS code in the victim's browser.
Jenkins Gitea Plugin does not implement trusted revisions, allowing attackers without commit access to the Git repo to change Jenkinsfiles even if Jenkins is configured to consider them to be untrusted.
Gitea allows 1FA for user accounts that have completed 2FA enrollment. If a user's credentials are known, then an attacker could send them to the API without requiring the 2FA one-time password.
models/repo_mirror.go in Gitea mishandles mirror repo URL settings, leading to remote code execution.
repo/setting.go in Gitea does not validate the form.MirrorAddress before calling SaveAddress.
Gitea contains a Incorrect Access Control vulnerability in Delete/Edit file functionallity that can result in the attacker deleting files outside the repository he/she has access to. This attack appears to be exploitable via the attacker must get write access to any repository including self-created ones.
Gitea allows remote code execution because it does not properly validate session IDs. This is related to session ID handling in the go-macaron/session code for Macaron.
Gitea version prior contains a vulnerability that can result in Exposure of users private email addresses.
An SSRF vulnerability in webhooks in Gitea and Gogs allows remote attackers to access intranet services.