CVE-2024-9512

| EUVD-2024-54676 MEDIUM
2025-06-12 [email protected]
5.3
CVSS 3.1
Share

CVSS Vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

4
Patch Released
Mar 31, 2026 - 21:13 nvd
Patch available
Analysis Generated
Mar 14, 2026 - 21:20 vuln.today
EUVD ID Assigned
Mar 14, 2026 - 21:20 euvd
EUVD-2024-54676
CVE Published
Jun 12, 2025 - 14:15 nvd
MEDIUM 5.3

Description

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 a secondary node is out of sync.

Analysis

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 a secondary node is out of sync.

Technical Context

A race condition occurs when the behavior of software depends on the timing of events, such as the order of execution of threads or processes.

Affected Products

Affected products: Gitlab Gitlab

Remediation

Use proper synchronization mechanisms (locks, mutexes, atomic operations). Implement file locking for filesystem operations. Avoid TOCTOU patterns.

Priority Score

27
Low Medium High Critical
KEV: 0
EPSS: +0.0
CVSS: +26
POC: 0

Vendor Status

Debian

gitlab
Release Status Fixed Version Urgency
sid fixed 17.6.5-19 -
(unstable) not-affected - -

Share

CVE-2024-9512 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy