Summary
Gogs OS Command Injection vulnerability
Workarounds
Disable repository upload.
References
https://huntr.dev/bounties/18cf9256-23ab-4098-a769-85f8da130f97/
For more information
If you have any questions or comments about this advisory, please post on https://github.com/gogs/gogs/issues/7030.
Impact
The malicious user is able to update a crafted config file into repository's .git directory in combination with crafted file deletion to gain SSH access to the server on case-insensitive file systems. All installations with repository upload enabled (default) on case-insensitive file systems (Windows, macOS, etc.) are affected.
Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.
CVE-2022-2024 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.12.11); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Make sanitization of upload path to .git directory to be case-insensitive. Users should upgrade to 0.12.11 or the latest 0.13.0+dev.
Frequently Asked Questions
- What is CVE-2022-2024? CVE-2022-2024 is a critical-severity OS command injection vulnerability in gogs.io/gogs (go), affecting versions < 0.12.11. It is fixed in 0.12.11. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
- How severe is CVE-2022-2024? CVE-2022-2024 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of gogs.io/gogs are affected by CVE-2022-2024? gogs.io/gogs (go) versions < 0.12.11 is affected.
- Is there a fix for CVE-2022-2024? Yes. CVE-2022-2024 is fixed in 0.12.11. Upgrade to this version or later.
- Is CVE-2022-2024 exploitable, and should I be worried? Whether CVE-2022-2024 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-2024 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-2024? Upgrade
gogs.io/gogsto 0.12.11 or later.