Security Resilience

CVE-2024-1947

Gitlab 13.2.4 – 16.10.6

Published
23 May 2024
Modified
13 December 2024
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0048 40th percentile
Risk Priority 37 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-1947 is a medium-severity Data Amplification (CWE-409) vulnerability in Gitlab Gitlab. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 40th 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 SC-5 (Denial-of-service Protection) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A denial of service (DoS) condition was discovered in GitLab CE/EE affecting all versions from 13.2.4 before 16.10.6, 16.11 before 16.11.3, and 17.0 before 17.0.1. By leveraging this vulnerability an attacker could create a DoS condition by sending crafted API…

more

calls.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
T1003.003 NTDS Credential Access
Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights.
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
T1003.007 Proc Filesystem Credential Access
Adversaries may gather credentials from the proc filesystem or `/proc`.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-2995Same product: Gitlab Gitlab
CVE-2023-5933Same product: Gitlab Gitlab
CVE-2026-1458Same product: Gitlab Gitlab
CVE-2025-10094Same product: Gitlab Gitlab
CVE-2026-1101Same product: Gitlab Gitlab
CVE-2025-14511Same product: Gitlab Gitlab
CVE-2026-1092Same product: Gitlab Gitlab
CVE-2025-14513Same product: Gitlab Gitlab
CVE-2025-2256Same product: Gitlab Gitlab
CVE-2025-13078Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
17.0.0 · 13.2.4 — 16.10.6 · 13.2.4 — 16.10.6 · 16.11.0 — 16.11.3

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Input validation can reject or limit decompression of data whose expansion ratio exceeds safe thresholds.

DoS protection limits the resource-exhaustion impact when a decompression bomb is processed.

Resource allocation controls bound memory/CPU consumption that a data-amplification attack would otherwise exhaust.

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.

DE.CM-09 partial match
blocks

Runtime monitoring of compute resources can detect exhaustion caused by decompression bombs.

PR.IR-04 partial match
blocks

Capacity planning and monitoring directly limits the availability impact of data-amplification attacks.

PR.PS-06 partial match
blocks

Secure-development practices include input-validation and resource-limit checks that prevent improper handling of compressed data.

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.

finds

Monitoring can detect anomalous resource usage but does not prevent the weakness.

blocks

Secure development lifecycle includes input validation and resource-limit checks that mitigate data-amplification attacks.

blocks

Application security requirements can mandate limits on decompression size and ratio.

blocks

Secure architecture principles encourage defensive design against resource-exhaustion threats.

References