CVE-2024-0231
Gitlab 12.0.0 – 17.0.5
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-0231 is a low-severity Resource Injection (CWE-99) vulnerability in Gitlab Gitlab. Its CVSS base score is 2.7 (Low).
Operationally, ranked at the 24th 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 SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-16029
Vulnerability Data
A resource misdirection vulnerability in GitLab CE/EE versions 12.0 prior to 17.0.5, 17.1 prior to 17.1.3, and 17.2 prior to 17.2.1 allows an attacker to craft a repository import in such a way as to misdirect commits.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation of inputs before they are accepted as resource identifiers.
Enforces authorizations on resource access so an injected identifier cannot reach outside the intended sphere.
Enforces information flow rules that block use of untrusted identifiers to reach unauthorized resources.
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.
Logging supports detection of injection attempts but does not prevent the weakness.
Monitoring activities can identify active injection attacks after they occur.
A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, testing (scans/penetration), and developer training that reduce the chance of introducing resource injection flaws, but does not guarantee their absence at runtime and leaves a bounded remainder (e.g. incomplete enforcement of input restrictions or flaws in non-development phases).
Application security requirements explicitly call for controls on external identifiers used to access resources.
A.8.27 mandates security-by-design principles (e.g. distrust external input, least privilege, fail securely, data validation/sanitization) and design reviews that can stop resource injection from reaching production, but this is only a minority slice of CWE-99 because the control sets process expectations rather than mandating any specific runtime enforcement mechanism that would block exploitation of every possible identifier misuse.
Secure coding standards require strict validation and whitelisting of all resource identifiers before use.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-99, a class-level weakness, and none of its children carries one either.
- No fine-grained STIG row for CWE-74, a class-level weakness, and none of its children carries one either.