CVE-2022-2992
Gitlab 11.10 – 15.1.6
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2022-2992 is a critical-severity Injection (CWE-74) vulnerability in Gitlab Gitlab. Its CVSS base score is 9.9 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
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 vulnerability tracked as CVE-2022-2992 affects GitLab Community Edition and Enterprise Edition in all versions from 11.10 up to but not including 15.1.6, as well as the 15.2.x and 15.3.x branches prior to 15.2.4 and 15.3.2 respectively. The flaw resides in the Import from GitHub API endpoint and permits an authenticated user to trigger remote code execution through unsafe deserialization, corresponding to CWE-74.
An attacker who already possesses a valid GitLab account can submit a crafted GitHub repository import request that results in arbitrary command execution on the server with the privileges of the GitLab application user, yielding full confidentiality, integrity, and availability impact across the instance.
Public advisories and the associated GitLab issue direct administrators to upgrade to one of the fixed releases (15.1.6, 15.2.4, or 15.3.2 or later) to eliminate the vulnerable code path; no other work-arounds are documented in the references.
The CVE carries a CVSS score of 9.9 and an EPSS score that has reached a peak of 0.9381 with a current value of 0.9119, while public exploit code and a detailed HackerOne report have been released.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-35210
Vulnerability Data
A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows an authenticated user to achieve remote code execution via the Import from GitHub API endpoint.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.1V1.2.3V1.2.5V1.2.8
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Developer assessments and testing (including injection-focused techniques) identify improper neutralization of special elements, and the verifiable flaw remediation corrects them pre-deployment.
Identifies indicators of injection attacks (command, SQL, LDAP, etc.) via anomaly and attack monitoring.
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.
Secure SDLC practices directly require input validation and output encoding that prevent injection flaws.
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 in development catches injection vulnerabilities before release.
Logging supports detection of injection attempts but does not prevent the weakness.
Monitoring activities can identify active injection attacks after they occur.
Secure development life cycle mandates input validation and output encoding that directly prevent injection flaws.
Application security requirements explicitly call for controls against injection attacks in software design.
Secure architecture principles reduce injection surfaces but do not prescribe specific neutralization techniques.