Gitea 1.9.5

CPE Details

Gitea 1.9.5
gitea
gitea
1.9.5
2020-05-21
18h09 +00:00
2020-05-21
18h09 +00:00
CPE NVD
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
Gestion des notifications

CPE Name: cpe:2.3:a:gitea:gitea:1.9.5:*:*:*:*:*:*:*

Informations

Vendor

gitea

Product

gitea

Version

1.9.5

Related CVE

Open and find in CVE List

CVE ID Publié Description Score Gravité
CVE-2022-38795 2023-08-06 22h00 +00:00 In Gitea through 1.17.1, repo cloning can occur in the migration function.
6.5
Moyen
CVE-2023-3515 2023-07-05 14h12 +00:00 Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4.
4.4
Moyen
CVE-2022-42968 2022-10-15 22h00 +00:00 Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.
9.8
Critique
CVE-2022-38183 2022-08-11 22h00 +00:00 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.
6.5
Moyen
CVE-2022-1928 2022-05-28 22h00 +00:00 Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9.
5.4
Moyen
CVE-2022-30781 2022-05-15 22h00 +00:00 Gitea before 1.16.7 does not escape git fetch remote.
7.5
Haute
CVE-2022-1058 2022-03-24 13h15 +00:00 Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5.
6.1
Moyen
CVE-2021-29134 2022-03-15 19h30 +00:00 The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL.
5.3
Moyen
CVE-2022-0905 2022-03-09 23h00 +00:00 Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4.
7.1
Haute
CVE-2021-45330 2022-02-09 16h16 +00:00 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.
9.8
Critique
CVE-2021-45327 2022-02-08 13h57 +00:00 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.
9.8
Critique
CVE-2021-3382 2021-02-05 14h15 +00:00 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.
7.5
Haute
CVE-2020-28991 2020-11-23 23h29 +00:00 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.
9.8
Critique
CVE-2020-14144 2020-10-16 11h02 +00:00 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). NOTE: The vendor has indicated this is not a vulnerability and states "This is a functionality of the software that is limited to a very limited subset of accounts. If you give someone the privilege to execute arbitrary code on your server, they can execute arbitrary code on your server. We provide very clear warnings to users around this functionality and what it provides.
7.2
Haute
CVE-2020-13246 2020-05-20 15h04 +00:00 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.
7.5
Haute