Bitnami package
gitea
pkg:bitnami/gitea
Vulnerabilities (73)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2022-0905 | Hig | 7.1 | < 1.16.4 | 1.16.4 | Mar 10, 2022 | Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4. | |
| CVE-2021-45331 | Cri | 9.8 | < 1.5.0 | 1.5.0 | Feb 9, 2022 | 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-2021-45330 | Cri | 9.8 | < 1.15.8 | 1.15.8 | Feb 9, 2022 | 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-45329 | Med | 6.1 | < 1.5.1 | 1.5.1 | Feb 8, 2022 | Cross Site Scripting (XSS) vulnerability exists in Gitea before 1.5.1 via the repository settings inside the external wiki/issue tracker URL field. | |
| CVE-2021-45328 | Med | 6.1 | < 1.4.3 | 1.4.3 | Feb 8, 2022 | Gitea before 1.4.3 is affected by URL Redirection to Untrusted Site ('Open Redirect') via internal URLs. | |
| CVE-2021-45327 | Cri | 9.8 | < 1.11.2 | 1.11.2 | Feb 8, 2022 | 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-45326 | Hig | 8.8 | < 1.5.2 | 1.5.2 | Feb 8, 2022 | Cross Site Request Forgery (CSRF) vulnerability exists in Gitea before 1.5.2 via API routes.This can be dangerous especially with state altering POST requests. | |
| CVE-2021-45325 | Hig | 7.5 | < 1.7.0 | 1.7.0 | Feb 8, 2022 | Server Side Request Forgery (SSRF) vulneraility exists in Gitea before 1.7.0 using the OpenID URL. | |
| CVE-2021-28378 | Low | 3.7 | >= 1.12.0, < 1.12.7 | 1.12.7 | Mar 15, 2021 | Gitea 1.12.x and 1.13.x before 1.13.4 allows XSS via certain issue data in some situations. | |
| CVE-2021-3382 | Hig | 7.5 | >= 1.9.0, < 1.13.2 | 1.13.2 | Feb 5, 2021 | 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. | |
| CVE-2020-28991 | Cri | 9.8 | >= 0.9.99, < 1.12.6 | 1.12.6 | Nov 24, 2020 | 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-2020-14144 | Hig | 7.2 | >= 1.1.0, < 1.12.6 | 1.12.6 | Oct 16, 2020 | 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 ENA | |
| CVE-2020-13246 | Hig | 7.5 | < 1.11.6 | 1.11.6 | May 20, 2020 | 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. |
- affected < 1.16.4fixed 1.16.4
Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4.
- affected < 1.5.0fixed 1.5.0
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.
- affected < 1.15.8fixed 1.15.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.
- affected < 1.5.1fixed 1.5.1
Cross Site Scripting (XSS) vulnerability exists in Gitea before 1.5.1 via the repository settings inside the external wiki/issue tracker URL field.
- affected < 1.4.3fixed 1.4.3
Gitea before 1.4.3 is affected by URL Redirection to Untrusted Site ('Open Redirect') via internal URLs.
- affected < 1.11.2fixed 1.11.2
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.
- affected < 1.5.2fixed 1.5.2
Cross Site Request Forgery (CSRF) vulnerability exists in Gitea before 1.5.2 via API routes.This can be dangerous especially with state altering POST requests.
- affected < 1.7.0fixed 1.7.0
Server Side Request Forgery (SSRF) vulneraility exists in Gitea before 1.7.0 using the OpenID URL.
- affected >= 1.12.0, < 1.12.7fixed 1.12.7
Gitea 1.12.x and 1.13.x before 1.13.4 allows XSS via certain issue data in some situations.
- affected >= 1.9.0, < 1.13.2fixed 1.13.2
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.
- affected >= 0.9.99, < 1.12.6fixed 1.12.6
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.
- affected >= 1.1.0, < 1.12.6fixed 1.12.6
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 ENA
- affected < 1.11.6fixed 1.11.6
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.
Page 4 of 4