CVE ID | Publié | Description | Score | Gravité |
---|---|---|---|---|
In Gitea through 1.17.1, repo cloning can occur in the migration function. | 6.5 |
Moyen |
||
Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4. | 4.4 |
Moyen |
||
Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled. | 9.8 |
Critique |
||
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 |
||
Cross-site Scripting (XSS) - Stored in GitHub repository go-gitea/gitea prior to 1.16.9. | 5.4 |
Moyen |
||
Gitea before 1.16.7 does not escape git fetch remote. | 7.5 |
Haute |
||
Open Redirect on login in GitHub repository go-gitea/gitea prior to 1.16.5. | 6.1 |
Moyen |
||
The avatar middleware in Gitea before 1.13.6 allows Directory Traversal via a crafted URL. | 5.3 |
Moyen |
||
Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4. | 7.1 |
Haute |
||
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 |
||
Gitea 1.12.x and 1.13.x before 1.13.4 allows XSS via certain issue data in some situations. | 5.4 |
Moyen |