Cyber Resilience

CVE-2024-4278

Gitlab 16.5.0 – 17.2.8

Published
26 September 2024
Modified
08 October 2024
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
EPSS Score 0.0023 14th percentile
Risk Priority 36 floored blend · peak EPSS

Summary

CVE-2024-4278 is a medium-severity Incorrect Synchronization (CWE-821) vulnerability in Gitlab Gitlab. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 14th 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 SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

An information disclosure issue has been discovered in GitLab EE affecting all versions starting from 16.5 prior to 17.2.8, from 17.3 prior to 17.3.4, and from 17.4 prior to 17.4.1. A maintainer could obtain a Dependency Proxy password by editing…

more

a certain Dependency Proxy setting.

CWE(s)
CWE-821NVD-CWE-Other

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-3607Same product: Gitlab Gitlab
CVE-2024-8114Same product: Gitlab Gitlab
CVE-2023-0805Same product: Gitlab Gitlab
CVE-2024-1539Same product: Gitlab Gitlab
CVE-2025-2246Same product: Gitlab Gitlab
CVE-2023-5612Same product: Gitlab Gitlab
CVE-2023-5600Same product: Gitlab Gitlab
CVE-2023-2233Same product: Gitlab Gitlab
CVE-2025-14103Same product: Gitlab Gitlab
CVE-2026-7492Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
17.4.0 · 16.5.0 — 17.2.8 · 17.3.0 — 17.3.4

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-4 Information in Shared System Resources partial match

SC-4 directly requires preventing unintended information transfer through shared resources, structurally blocking the concurrent unsynchronized access described by CWE-821.

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 correct concurrency controls and synchronization primitives to prevent 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.

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

Security testing can detect synchronization flaws before production deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC practices include concurrency and synchronization requirements that reduce race conditions.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate proper locking and thread-safety controls.

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

Secure architecture principles address concurrent access and resource synchronization.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require correct synchronization primitives and thread-safety.

A.8.32 Change management none match
none

Change management processes can introduce or miss synchronization fixes during updates.

References