Cyber Resilience

CVE-2024-9512

Race Condition in Gitlab ≤ 17.10.8

Published
12 June 2025
Modified
17 June 2026
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0022 13th percentile
Risk Priority 40 floored blend · peak EPSS

Summary

CVE-2024-9512 is a medium-severity Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367) vulnerability in Gitlab Gitlab. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 13th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-25 (Reference Monitor) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

An issue has been discovered in GitLab EE affecting all versions prior to 17.10.8, 17.11 prior to 17.11.4, and 18.0 prior to 18.0.2. It may have been possible for private repository to be cloned in case of race condition when…

more

a secondary node is out of sync.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1034 Path Interception Persistence
**This technique has been deprecated.
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
T1574 Hijack Execution Flow Stealth
Adversaries may execute their own malicious payloads by hijacking the way operating systems run programs.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-9183Same product: Gitlab Gitlab
CVE-2024-9633Same product: Gitlab Gitlab
CVE-2025-5069Same product: Gitlab Gitlab
CVE-2023-4008Same product: Gitlab Gitlab
CVE-2023-0989Same product: Gitlab Gitlab
CVE-2024-4278Same product: Gitlab Gitlab
CVE-2023-6477Same product: Gitlab Gitlab
CVE-2023-2485Same product: Gitlab Gitlab
CVE-2024-12303Same product: Gitlab Gitlab
CVE-2026-8716Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
≤ 17.10.8 · ≤ 17.10.8 · 17.11.0 — 17.11.4

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)
  • V15.4.2
  • V17.2.6

Mitigating Controls (NIST 800-53 r5) AI

A reference monitor that is always invoked and analyzable structurally eliminates the non-atomic check-then-use pattern underlying TOCTOU.

Access enforcement that performs an atomic check-and-use decision directly stops the window in which a TOCTOU race can be exploited.

Process isolation limits the blast radius of a successful TOCTOU exploitation but does not remove the race itself.

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 include coding standards and reviews that prevent TOCTOU race conditions.

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.

none

Reliable, synchronized time across systems narrows the exploitable window in which a resource state can change between a security check and its use.

References