Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
105 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
In Gitea before 1.25.2, /api/v1/user has different responses for failed authentication depending on whether a username exists.
Recommended action: Upgrade to 1.25.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
In Gitea before 1.21.2, an anonymous user can visit a private user's project.
Recommended action: Upgrade to 1.21.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries.
Recommended action: Upgrade to 1.22.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Gitea before 1.21.8 inadvertently discloses users' login times by allowing (for example) the lastlogintime explore/users sort order.
Recommended action: Upgrade to 1.21.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
In Gitea before 1.20.1, a forbidden URL scheme such as javascript: can be used for a link, aka XSS.
Recommended action: Upgrade to 1.20.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Gitea before 1.22.2 allows XSS because the search input box (for creating tags and branches) is v-html instead of v-text.
Recommended action: Upgrade to 1.22.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Gitea before 1.23.0 allows attackers to add attachments with forbidden file extensions by editing an attachment name via an attachment API.
Recommended action: Upgrade to 1.23.0-rc0 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
In Gitea before 1.22.5, branch deletion permissions are not adequately enforced after merging a pull request.
Recommended action: Upgrade to 1.22.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Gitea before 1.22.3 mishandles access to a private resource upon receiving an API token with scope limited to public resources.
Recommended action: Upgrade to 1.22.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Gitea before 1.25.2 mishandles authorization for deletion of releases.
Recommended action: Upgrade to 1.25.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Gitea Gitea Open Source Git Server allows Stored XSS.This issue affects Gitea Open Source Git Server: 1.22.0.
Recommended action: Upgrade to 1.22.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The git hook feature in Gitea 1.1.0 through 1.12.5 allows for authenticated remote code execution.
Recommended action: Upgrade to 1.12.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
In Gitea through 1.17.1, repo cloning can occur in the migration function.
Recommended action: Upgrade to 1.17.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4. This is most likely a post-auth redirect plus it is a POST based request scenario, so less likely that can be exploited or chained with other bugs that can cause phishing or credential theft.
Recommended action: Upgrade to 1.19.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
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.
Recommended action: Upgrade to 1.16.9 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9 via unfiltered pdfs
Recommended action: Upgrade to 1.16.9 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Gitea 1.7.0 and earlier is affected by: Cross Site Scripting (XSS). The impact is: Attacker is able to have victim execute arbitrary JS in browser. The component is: go-get URL generation - PR to fix: https://github.com/go-gitea/gitea/pull/5905. The attack vector is: victim must open a specifically crafted URL. The fixed version is: 1.7.1 and later.
Recommended action: Upgrade to 1.7.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Gitea 1.7.2, 1.7.3 is affected by: Cross Site Scripting (XSS). The impact is: execute JavaScript in victim's browser, when the vulnerable repo page is loaded. The component is: repository's description. The attack vector is: victim must navigate to public and affected repo page.
Recommended action: Upgrade to 1.7.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Gitea before 1.8.0 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.
Recommended action: Upgrade to 1.8.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Gitea before 1.16.7 does not escape the shell out for git fetch remote allowing for shell command injection
Recommended action: Upgrade to 1.16.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
An SSRF vulnerability in webhooks in Gitea through 1.5.0-rc2 and Gogs through 0.11.53 allows remote attackers to access intranet services.
Recommended action: Upgrade to 1.16.0-rc1 (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Gitea version 1.6.2 and earlier 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. This vulnerability appears to have been fixed in 1.6.3, 1.7.0-rc2.
Recommended action: Upgrade to 1.6.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file.
Recommended action: Upgrade to 1.16.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5.
Recommended action: Upgrade to 1.16.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL.
Recommended action: Upgrade to 1.13.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.