First published: Thu Aug 22 2024(Updated: )
An issue was discovered in GitLab CE/EE affecting all versions starting from 8.2 prior to 17.1.6 starting from 17.2 prior to 17.2.4, and starting from 17.3 prior to 17.3.1, which allows an attacker to create a branch with the same name as a deleted tag.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=8.2.0<17.1.6 | |
GitLab | >=17.2.0<17.2.4 | |
GitLab | >=17.3.0<17.3.1 | |
GitLab | >=8.2.0<17.1.6 | |
GitLab | >=17.2.0<17.2.4 | |
GitLab | >=17.3.0<17.3.1 |
Upgrade to versions 17.1.6, 17.2.4, 17.3.1 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-6502 is classified as a moderate severity vulnerability due to its potential to disrupt branch management in GitLab.
To mitigate CVE-2024-6502, upgrade GitLab to version 17.1.6 or later, 17.2.4 or later, or 17.3.1 or later.
CVE-2024-6502 affects GitLab CE/EE versions from 8.2 up to, but not including, 17.1.6, 17.2.0 to 17.2.4, and 17.3.0 to 17.3.1.
CVE-2024-6502 allows an attacker to create a branch with the same name as a deleted tag, potentially leading to confusion and unauthorized access.
Yes, CVE-2024-6502 affects both GitLab Community Edition (CE) and Enterprise Edition (EE) across the specified versions.