Bitnami package
gitea
pkg:bitnami/gitea
Vulnerabilities (42)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-3515 | — | < 1.19.4 | 1.19.4 | Jul 5, 2023 | Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4. | ||
| CVE-2022-46685 | — | < 1.4.5 | 1.4.5 | Dec 7, 2022 | 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. | ||
| CVE-2022-42968 | — | < 1.17.3 | 1.17.3 | Oct 16, 2022 | Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled. | ||
| CVE-2022-38183 | — | < 1.16.9 | 1.16.9 | Aug 12, 2022 | 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 | ||
| CVE-2022-1928 | — | < 1.16.9 | 1.16.9 | May 29, 2022 | Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9. | ||
| CVE-2022-30781 | — | < 1.16.7 | 1.16.7 | May 16, 2022 | Gitea before 1.16.7 does not escape git fetch remote. | ||
| CVE-2022-27313 | — | >= 1.16.3, < 1.16.4 | 1.16.4 | May 3, 2022 | An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file. | ||
| CVE-2022-1058 | — | < 1.16.5 | 1.16.5 | Mar 24, 2022 | Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5. | ||
| CVE-2021-29134 | — | < 1.13.6 | 1.13.6 | Mar 15, 2022 | The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL. | ||
| CVE-2022-0905 | — | < 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 | — | < 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 | — | < 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 | — | < 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 | — | < 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 | — | < 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 | — | < 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 | — | < 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 | — | >= 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 | — | >= 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 | — | >= 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-2023-3515Jul 5, 2023affected < 1.19.4fixed 1.19.4
Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4.
- CVE-2022-46685Dec 7, 2022affected < 1.4.5fixed 1.4.5
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.
- CVE-2022-42968Oct 16, 2022affected < 1.17.3fixed 1.17.3
Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.
- CVE-2022-38183Aug 12, 2022affected < 1.16.9fixed 1.16.9
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
- CVE-2022-1928May 29, 2022affected < 1.16.9fixed 1.16.9
Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9.
- CVE-2022-30781May 16, 2022affected < 1.16.7fixed 1.16.7
Gitea before 1.16.7 does not escape git fetch remote.
- CVE-2022-27313May 3, 2022affected >= 1.16.3, < 1.16.4fixed 1.16.4
An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers to cause a Denial of Service (DoS) via deleting the configuration file.
- CVE-2022-1058Mar 24, 2022affected < 1.16.5fixed 1.16.5
Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5.
- CVE-2021-29134Mar 15, 2022affected < 1.13.6fixed 1.13.6
The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL.
- CVE-2022-0905Mar 10, 2022affected < 1.16.4fixed 1.16.4
Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4.
- CVE-2021-45331Feb 9, 2022affected < 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.
- CVE-2021-45330Feb 9, 2022affected < 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.
- CVE-2021-45329Feb 8, 2022affected < 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.
- CVE-2021-45328Feb 8, 2022affected < 1.4.3fixed 1.4.3
Gitea before 1.4.3 is affected by URL Redirection to Untrusted Site ('Open Redirect') via internal URLs.
- CVE-2021-45327Feb 8, 2022affected < 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.
- CVE-2021-45326Feb 8, 2022affected < 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.
- CVE-2021-45325Feb 8, 2022affected < 1.7.0fixed 1.7.0
Server Side Request Forgery (SSRF) vulneraility exists in Gitea before 1.7.0 using the OpenID URL.
- CVE-2021-28378Mar 15, 2021affected >= 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.
- CVE-2021-3382Feb 5, 2021affected >= 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.
- CVE-2020-28991Nov 24, 2020affected >= 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.
Page 2 of 3