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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-14144US | high7.2 | Exploit | ||
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., on… | ||||
references
External citations — patches, advisories, analysis.
- http://packetstormsecurity.com/files/162122/Gitea-Git-Hooks-Remote-Code-Execution.htmlADVISORY
- https://docs.github.com/en/enterprise-server%402.19/admin/policies/creating-a-pre-receive-hook-scriptWEB
- https://docs.gitlab.com/ee/administration/server_hooks.htmlADVISORY
- https://github.com/PandatiX/CVE-2021-28378ADVISORY
- https://github.com/PandatiX/CVE-2021-28378#notesADVISORY
- https://github.com/go-gitea/gitea/pull/13058ADVISORY
- https://github.com/go-gitea/gitea/releasesADVISORY
- https://nvd.nist.gov/vuln/detail/CVE-2020-14144WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan