First published: Thu Aug 08 2024(Updated: )
A permission check vulnerability in GitLab CE/EE affecting all versions starting from 8.12 prior to 17.0.6, 17.1 prior to 17.1.4, and 17.2 prior to 17.2.2 allowed for LFS tokens to read and write to the user owned repositories.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=8.12.0<17.0.6 | |
GitLab | >=8.12.0<17.0.6 | |
GitLab | >=17.1<17.1.4 | |
GitLab | >=17.1.0<17.1.4 | |
GitLab | >=17.2.0<17.2.2 |
Upgrade to versions 17.2.2, 17.1.4, 17.0.6 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-3035 is classified as a medium severity vulnerability due to its ability to allow unauthorized access to user-owned repositories.
To fix CVE-2024-3035, you should upgrade GitLab to version 17.0.6, 17.1.4, or 17.2.2 or later.
CVE-2024-3035 affects all versions of GitLab from 8.12 to prior 17.0.6, and specific versions 17.1 and 17.2 before 17.1.4 and 17.2.2 respectively.
CVE-2024-3035 is a permission check vulnerability that allows unauthorized LFS token access to user repositories.
There is no specific workaround for CVE-2024-3035; the best solution is to apply the recommended software update.