gitea: Gitea: Unauthorized access to private resources via public-scoped API tokens

Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources.

gitea: Gitea: Cross-Site Scripting (XSS) vulnerability via search input

Gitea before 1.22.2 allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text.

gitea: Gitea: Information disclosure of user login times via sort order

Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order.

gitea: Gitea: Access control bypass in package registries

Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries.

gitea: Gitea: Information disclosure via anonymous access to private user projects

In Gitea before 1.21.2, an anonymous user can visit a private user's project.

gitea: Gitea: Cross-Site Scripting (XSS) via forbidden URL scheme in links

In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS.

gitea: Sanitize and Escape refs in git backend

Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.

In Jenkins Gitea Plugin 1.4.4 and earlier, the implementation of Gitea personal access tokens did not support credentials masking, potentially exposing them through the build log.

Open Redirect in go-gitea/gitea

Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4.

In Gitea through 1.17.1, repo cloning can occur in the migration function.

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.

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.

Cross-site Scripting (XSS) - Stored in go-gitea/gitea

Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9.

Open Redirect on login in go-gitea/gitea

Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5.

Missing Authorization in go-gitea/gitea

Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4.

An Authentication Bypass vulnerability exists in Gitea before 1.5.0, which could let a malicious user gain privileges. If captured, the TOTP code for the 2FA can be submitted correctly more than once.

An issue exsits in Gitea through 1.15.7, 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.

Cross Site Scripting (XSS) vulnerability exists in Gitea before 1.5.1 via the repository settings inside the external wiki/issue tracker URL field.

Gitea before 1.4.3 is affected by URL Redirection to Untrusted Site ('Open Redirect') via internal URLs.