Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2022-2185 is a critical-severity OS Command Injection (CWE-78) vulnerability in Gitlab Gitlab. Its CVSS base score is 9.9 (Critical).
Operationally, ranked in the top 0.5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-2 (Flaw Remediation) — 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.
A critical vulnerability tracked as CVE-2022-2185 affects GitLab Community and Enterprise Editions in all versions from 14.0 prior to 14.10.5, from 15.0 prior to 15.0.4, and from 15.1 prior to 15.1.1. The flaw, assigned CWE-78, permits an authenticated user who is authorized to import projects to supply a maliciously crafted project file that triggers remote code execution on the server. It carries a CVSS 3.1 base score of 9.9, reflecting network attack vector, low complexity, and full confidentiality, integrity, and availability impact under a changed scope.
An attacker with a low-privileged GitLab account that includes project-import rights can upload the crafted archive through the normal import workflow. Successful exploitation results in arbitrary command execution on the underlying GitLab host, potentially allowing the attacker to read or modify repositories, pivot within the instance, or fully compromise the server.
Official GitLab advisories and the associated security release notes direct administrators to upgrade immediately to 14.10.5, 15.0.4, or 15.1.1 or later, depending on the branch in use. The referenced CVE JSON and issue trackers confirm that the fixes address the unsafe handling of imported project data that led to the command-injection condition. The EPSS score has reached a peak of 0.9403 with a current value of 0.8696, indicating sustained exploitation interest after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-34469
Vulnerability Data
A critical issue has been discovered in GitLab affecting all versions starting from 14.0 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 where an authenticated user authorized to import projects could import a maliciously crafted project…
more
leading to remote code execution.
- 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 requires timely application of the vendor patches (14.10.5/15.0.4/15.1.1) that eliminate the unsafe deserialization and command-injection path in the project-import workflow.
Mandates validation and sanitization of all input from imported project archives, blocking the maliciously crafted payloads that trigger CWE-78 command execution.
Requires automated malicious-code detection mechanisms that can inspect or sandbox project-import files before they are processed by the GitLab importer.
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.