Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-2024 is a critical-severity OS Command Injection (CWE-78) vulnerability in Gogs Gogs. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 0.1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2022-2024 is an OS command injection vulnerability, tracked as CWE-78, that affects the Gogs Git service in all versions prior to 0.12.11. The flaw received a CVSS v3.1 base score of 9.8, reflecting network-accessible attack vectors that require no authentication or user interaction.
An unauthenticated remote attacker can supply crafted input that results in arbitrary operating-system command execution on the underlying host, granting full control over confidentiality, integrity, and availability of the affected system.
The referenced commit 15d0d6a94be0098a8227b6b95bdf2daed105ec41 in the Gogs repository addresses the issue; administrators should upgrade to release 0.12.11 or later. The associated huntr.dev report provides additional technical detail on the injection point.
The EPSS score has reached a peak of 0.4526 with a current value of 0.4364, indicating sustained exploitation interest after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-0760
Vulnerability Data
OS Command Injection in GitHub repository gogs/gogs prior to 0.12.11.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly blocks the crafted input that triggers OS command injection (CWE-78) before it reaches the shell.
Limits the privileges of the Gogs process so that even a successful injection cannot obtain full host control.
Enables detection of anomalous command execution or unexpected process behavior resulting from the injection.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.PS-06's SDLC practices directly require secure coding and input handling that blocks command-injection defects, yet the single broad outcome leaves many specific neutralization vectors and verification gaps unaddressed.
Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.