Gitea 1.15.5

CPE Details

Gitea 1.15.5
gitea
gitea
1.15.5
2022-02-09
11h09 +00:00
2022-02-09
11h14 +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.15.5:*:*:*:*:*:*:*

Informations

Vendor

gitea

Product

gitea

Version

1.15.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-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