First published: Thu Oct 10 2024(Updated: )
An issue has been discovered in GitLab EE affecting all versions starting from 16.6 prior to 17.2.9, from 17.3 prior to 17.3.5, and from 17.4 prior to 17.4.2. It was possible for an unauthenticated attacker to determine the GitLab version number for a GitLab instance.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=16.6.0<17.2.9 | |
GitLab | >=17.3.0<17.3.5 | |
GitLab | >=17.4.0<17.4.2 |
Upgrade to version 17.2.9, 17.3.5 or 17.4.2
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-9596 is classified as a low-severity vulnerability affecting specific GitLab EE versions.
To fix CVE-2024-9596, upgrade GitLab EE to version 17.2.9, 17.3.5, or 17.4.2 or later.
CVE-2024-9596 affects GitLab EE versions from 16.6 prior to 17.2.9, 17.3 prior to 17.3.5, and 17.4 prior to 17.4.2.
Yes, an unauthenticated attacker can exploit CVE-2024-9596 to determine the GitLab version number.
No specific workarounds are provided for CVE-2024-9596; upgrading is the recommended solution.