Note:
This project will be discontinued after December 13, 2021. [more]
Product:
Gitea
(Gitea)Repositories |
Unknown: This might be proprietary software. |
#Vulnerabilities | 33 |
Date | Id | Summary | Products | Score | Patch | Annotated |
---|---|---|---|---|---|---|
2020-10-16 | CVE-2020-14144 | 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... | Gitea | 7.2 | ||
2023-07-05 | CVE-2023-3515 | Open Redirect in GitHub repository go-gitea/gitea prior to 1.19.4. | Gitea | 4.4 | ||
2019-05-31 | CVE-2019-10330 | Jenkins Gitea Plugin 1.1.1 and earlier did not implement trusted revisions, allowing attackers without commit access to the Git repo to change Jenkinsfiles even if Jenkins is configured to consider them to be untrusted. | Gitea | 7.5 | ||
2022-02-08 | CVE-2021-45327 | 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. | Gitea | 9.8 | ||
2022-08-12 | CVE-2022-38183 | 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. | Gitea | 6.5 | ||
2023-08-07 | CVE-2022-38795 | In Gitea through 1.17.1, repo cloning can occur in the migration function. | Gitea | 6.5 | ||
2022-03-10 | CVE-2022-0905 | Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4. | Gitea | 7.1 | ||
2022-05-16 | CVE-2022-30781 | Gitea before 1.16.7 does not escape git fetch remote. | Gitea | 7.5 | ||
2022-12-12 | CVE-2022-46685 | 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. | Gitea | 4.3 | ||
2022-10-16 | CVE-2022-42968 | Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled. | Gitea | 9.8 |