Gogs allows argument Injection when tagging new releases
### Impact Unprivileged user accounts with at least one SSH key can read arbitrary files on the system. For instance, they could leak the configuration files that could contain database credentials (`[database] *`) and `[security] SECRET_KEY`. Attackers could also exfiltrate TLS certificates, other users' repositories, and the Gogs database when the SQLite driver is enabled. ### Patches Unintended Git options has been ignored for creating tags (https://github.com/gogs/gogs/pull/7872). Users should upgrade to 0.13.1 or the latest 0.14.0+dev. ### Workarounds No viable workaround available, please only grant access to trusted users to your Gogs instance on affected versions. ### References https://www.cve.org/CVERecord?id=CVE-2024-39933
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-39933US | high7.7 | — | ||
Gogs through 0.13.0 allows argument injection during the tagging of a new release. | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/gogs/gogsPACKAGE
- https://github.com/gogs/gogs/commit/76831d0d06c44c5cf46dc22b380440b7507c2f07WEB
- https://github.com/gogs/gogs/pull/7872WEB
- https://github.com/gogs/gogs/security/advisories/GHSA-m27m-h5gj-wwmgWEB
- https://nvd.nist.gov/vuln/detail/CVE-2024-39933ADVISORY
- https://www.sonarsource.com/blog/securing-developer-tools-unpatched-code-vulnerabilities-in-gogs-1WEB
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