CVE search
Every published CVE plus open-source advisories (NVD, OSV, GitHub), with CVSS, EPSS and whether it is being exploited in the wild (CISA KEV). Updated every few hours. Our scans match these against the technologies they detect.
Every published CVE plus open-source advisories (NVD, OSV, GitHub), with CVSS, EPSS and whether it is being exploited in the wild (CISA KEV). Updated every few hours. Our scans match these against the technologies they detect.
| CVE-2022-42968 |
| 심각9.8 |
Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled. |
| 16/10/2022 |
| CVE-2022-38183 | 보통6.5 | 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. | 12/08/2022 |
| CVE-2022-1928 | 보통5.4 | Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9. | 29/05/2022 |
| CVE-2022-30781 | 높음7.5 | Gitea before 1.16.7 does not escape git fetch remote. | 16/05/2022 |
| CVE-2022-27313 | 높음7.5 | An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file. | 03/05/2022 |
| CVE-2022-1058 | 보통6.1 | Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5. | 24/03/2022 |
| CVE-2021-29134 | 보통5.3 | The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL. | 15/03/2022 |
| CVE-2022-0905 | 높음7.1 | Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4. | 10/03/2022 |
| CVE-2021-45331 | 심각9.8 | 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. | 09/02/2022 |
| CVE-2021-45330 | 심각9.8 | 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. | 09/02/2022 |
| CVE-2021-45327 | 심각9.8 | Gitea before 1.11.2 is affected by Trusting HTTP Permission Methods on the Server Side when referencing the vulnerable admin or user API. which could let a remote malisious user execute arbitrary code. | 08/02/2022 |
| CVE-2021-28378 | 보통5.4 | Gitea 1.12.x and 1.13.x before 1.13.4 allows XSS via certain issue data in some situations. | 15/03/2021 |
| CVE-2021-3382 | 높음7.5 | Stack buffer overflow vulnerability in gitea 1.9.0 through 1.13.1 allows remote attackers to cause a denial of service (crash) via vectors related to a file path. | 05/02/2021 |
| CVE-2020-14144 | 높음7.2 | The git hook feature in Gitea 1.1.0 through 1.12.5 might allow for authenticated remote code execution in customer environments where the documentation was not understood (e.g., one viewpoint is that the dangerousness of this feature should be documented immediately above the ENABLE_GIT_HOOKS line in the config file). | 16/10/2020 |
| CVE-2020-13246 | 높음7.5 | An issue was discovered in Gitea through 1.11.5. An attacker can trigger a deadlock by initiating a transfer of a repository's ownership from one organization to another. | 20/05/2020 |
| CVE-2019-1010261 | 보통6.1 | 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 fix | 18/07/2019 |