First published: Tue Nov 26 2024(Updated: )
An issue was discovered in GitLab CE/EE affecting all versions starting from 15.6 prior to 17.4.5, starting from 17.5 prior to 17.5.3, starting from 17.6 prior to 17.6.1 which could cause Denial of Service via integrating a malicious harbor registry.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=15.6.0<17.4.5 | |
GitLab | >=15.6.0<17.4.5 | |
GitLab | >=17.5.0<17.5.3 | |
GitLab | >=17.5.0<17.5.3 | |
GitLab | =17.6.0 | |
GitLab | =17.6.0 |
Upgrade to versions 17.4.5, 17.5.3, 17.6.1 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-8177 has been classified as a medium severity vulnerability affecting GitLab.
To fix CVE-2024-8177, upgrade GitLab to version 17.4.5 or later, 17.5.3 or later, or 17.6.1 or later.
If affected by CVE-2024-8177, exploiting the vulnerability might lead to a Denial of Service for GitLab.
CVE-2024-8177 affects all GitLab versions from 15.6.0 up to but not including 17.4.5, 17.5.3, and 17.6.1.
Currently, the recommended approach is to upgrade GitLab, as no specific workaround has been provided for CVE-2024-8177.