Filtered by vendor Gitea
Subscribe
Search
Total
6 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2021-45327 | 1 Gitea | 1 Gitea | 2023-08-08 | 7.5 HIGH | 9.8 CRITICAL |
| 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. | |||||
| CVE-2021-45330 | 1 Gitea | 1 Gitea | 2022-07-12 | 7.5 HIGH | 9.8 CRITICAL |
| 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. | |||||
| CVE-2021-45331 | 1 Gitea | 1 Gitea | 2022-02-14 | 7.5 HIGH | 9.8 CRITICAL |
| 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. | |||||
| CVE-2020-28991 | 1 Gitea | 1 Gitea | 2020-12-03 | 7.5 HIGH | 9.8 CRITICAL |
| Gitea 0.9.99 through 1.12.x before 1.12.6 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. | |||||
| CVE-2019-11576 | 1 Gitea | 1 Gitea | 2020-08-24 | 7.5 HIGH | 9.8 CRITICAL |
| 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. | |||||
| CVE-2018-18926 | 1 Gitea | 1 Gitea | 2019-01-29 | 7.5 HIGH | 9.8 CRITICAL |
| Gitea before 1.5.4 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. | |||||