Cyber Resilience

CVE-2024-8402

Command Injection in Gitlab 17.2.0 – 17.7.7

Public PoCCommand Injection
Published
13 March 2025
Modified
08 August 2025
CVSS Score v3.1 3.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N
EPSS Score 0.0024 15th percentile
Risk Priority 28 floored blend · peak EPSS

Summary

CVE-2024-8402 is a low-severity Command Injection (CWE-77) vulnerability in Gitlab Gitlab. Its CVSS base score is 3.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 15th percentile by exploit likelihood (below the median); 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 SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — 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-2024-8402 is an input validation issue in the Google Cloud IAM integration feature of GitLab Enterprise Edition (EE). It affects all versions starting from 17.2 before 17.7.7, all versions starting from 17.8 before 17.8.5, and all versions starting from 17.9 before 17.9.2. Classified as CWE-77 (Command Injection), the vulnerability carries a CVSS v3.1 base score of 3.7 (AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N).

Exploitation requires a Maintainer with local access to perform a high-complexity attack involving user interaction. Successful exploitation enables the Maintainer to introduce malicious code through the flawed input validation in the Google Cloud IAM integration.

Advisories recommend upgrading to patched versions: 17.7.7 or later for the 17.2 series, 17.8.5 or later for the 17.8 series, and 17.9.2 or later for the 17.9 series. Further details on the issue and resolution are documented in the GitLab issue tracker at https://gitlab.com/gitlab-org/gitlab/-/issues/482813 and the HackerOne disclosure report at https://hackerone.com/reports/2601569.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

An issue was discovered in GitLab EE affecting all versions starting from 17.2 before 17.7.7, all versions starting from 17.8 before 17.8.5, all versions starting from 17.9 before 17.9.2. An input validation issue in the Google Cloud IAM integration feature…

more

could have enabled a Maintainer to introduce malicious code.

CWE(s)
CWE-77

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
attack.mitre.org →
T1059.003 Windows Command Shell Execution
Adversaries may abuse the Windows command shell for execution.
attack.mitre.org →
T1059.004 Unix Shell Execution
Adversaries may abuse Unix shell commands and scripts for execution.
attack.mitre.org →
T1059.008 Network Device CLI Execution
Adversaries may abuse scripting or built-in command line interpreters (CLI) on network devices to execute malicious command and payloads.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-9773Same product: Gitlab Gitlab
CVE-2025-6945Same product: Gitlab Gitlab
CVE-2024-8640Same product: Gitlab Gitlab
CVE-2024-7110Same product: Gitlab Gitlab
CVE-2023-1708Same product: Gitlab Gitlab
CVE-2022-2884Same product: Gitlab Gitlab
CVE-2022-2185Same product: Gitlab Gitlab
CVE-2024-0231Same product: Gitlab Gitlab
CVE-2021-22205Same product: Gitlab Gitlab
CVE-2026-1516Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
17.2.0 — 17.7.7 · 17.8.0 — 17.8.5 · 17.9.0 — 17.9.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

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

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover command-construction flaws before deployment.

SI-10 Information Input Validation good match

Input validation directly stops construction of commands from untrusted data containing special elements.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles include proper neutralization and safe command construction practices.

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

Secure SDLC practices directly require input validation and neutralization that prevent command injection.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data can detect anomalous command execution resulting from injection.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.

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.

A.8.28 Secure coding mostly match
prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches command-injection vulnerabilities before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection flaws including command injection.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.

A.8.31 Separation of development, test and production environments none match
none

Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.

References