Cyber Resilience

CVE-2022-2884

RCE in Gitlab 11.3.4 – 15.1.5

Public PoCHigh EPSSRCECommand Injection
Published
17 October 2022
Modified
14 May 2025
CVSS Score v3.1 9.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.76 99.5th percentile
Risk Priority 92 floored blend · peak EPSS

Summary

CVE-2022-2884 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; a public proof-of-concept is referenced.

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.

CVE-2022-2884 is an OS command injection vulnerability, tracked as CWE-78, that affects GitLab Community Edition and Enterprise Edition. It impacts all versions from 11.3.4 up to but not including 15.1.5, as well as the 15.2.x series through 15.2.3 and the 15.3.x series through 15.3.1. The flaw resides in the Import from GitHub API endpoint and carries a CVSS 3.1 score of 9.9.

An authenticated user can send a crafted request to the affected endpoint and obtain remote code execution on the GitLab instance with the privileges of the application user. Because the attack requires only low-privileged authenticated access and no user interaction, it can be performed over the network with limited effort.

Public references, including the official GitLab CVE record and the associated security issue, indicate that the vulnerability is resolved by upgrading to the fixed releases 15.1.5, 15.2.3, or 15.3.1 and later. A working proof-of-concept exploit has been published on Packet Storm, and the issue was originally reported through HackerOne.

EPSS for this CVE rose sharply from low values to a peak of 0.7478 on 2025-12-11 before receding to the current score of 0.3003, indicating a clear surge in exploitation interest after disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability in GitLab CE/EE affecting all versions from 11.3.4 prior to 15.1.5, 15.2 to 15.2.3, 15.3 to 15.3 to 15.3.1 allows an an authenticated user to achieve remote code execution via the Import from GitHub API endpoint

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.

T1190 Exploit Public-Facing Application Initial Accessconfidence: HIGH
The vulnerability is an unauthenticated-accessible remote code execution flaw in a public-facing GitLab API endpoint.
T1059 Command and Scripting Interpreter Executionconfidence: HIGH
Successful exploitation results in arbitrary OS command execution on the GitLab server.
T1068 Exploitation for Privilege Escalation Privilege Escalationconfidence: MEDIUM
RCE is achieved with the privileges of the application user, which may allow privilege escalation depending on the deployment context.
inferred from description + CWE · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2022-2185Same product: Gitlab Gitlab
CVE-2024-4207Same product: Gitlab Gitlab
CVE-2023-5963Same product: Gitlab Gitlab
CVE-2024-2454Same product: Gitlab Gitlab
CVE-2025-11042Same product: Gitlab Gitlab
CVE-2023-6195Same product: Gitlab Gitlab
CVE-2025-11989Same product: Gitlab Gitlab
CVE-2026-1747Same product: Gitlab Gitlab
CVE-2024-7296Same product: Gitlab Gitlab
CVE-2023-0155Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
11.3.4 — 15.1.5 · 11.3.4 — 15.1.5 · 15.2 — 15.2.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SI-2 Flaw Remediation
  • CM-7 Least Functionality
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.2.5
  • V1.2.8
  • V15.2.5

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires validation and sanitization of untrusted input to the GitHub import API endpoint, blocking the crafted command-injection payload that leads to RCE.

prevent

Mandates timely application of vendor patches that eliminate the OS command-injection flaw in the affected GitLab import endpoint.

prevent

Restricts activation or exposure of non-essential GitLab import functionality, reducing the attack surface available to authenticated users.

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 mostly match
prevents

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.

PR.PS-02 partial match
prevents

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.

detects

Security testing and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.

References