🛡️ CVE-2024-4278 — gitlab
Description
Incorrect Synchronization in GitLab
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 a certain Dependency Proxy setting.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs administrative privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality low, integrity low, availability none.
Weakness class
CVE-2024-4278 is classified as CWE-821: Incorrect Synchronization. The product utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource.
Affected software
CVE-2024-4278 is recorded against 1 package.
- gitlab
Timeline and source
Published on 27 September 2024 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
Details
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| gitlab | — | — |
References
Similar Threats
- High CVE-2020-10073
- Critical CVE-2020-10074
- Medium CVE-2020-10075
- Medium CVE-2020-10076
- Critical CVE-2020-10077
Free Vulnerability Check
Is your site affected by CVE-2024-4278?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2024-4278 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.