CVE-2024-9596: Inclusion of Sensitive Information in Source Code in GitLab
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.
Affected Software
Remediation
Information
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2024-9596?
CVE-2024-9596 is classified as a low-severity vulnerability affecting specific GitLab EE versions.
How do I fix CVE-2024-9596?
To fix CVE-2024-9596, upgrade GitLab EE to version 17.2.9, 17.3.5, or 17.4.2 or later.
What versions of GitLab are affected by CVE-2024-9596?
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.
Can an attacker exploit CVE-2024-9596 without authentication?
Yes, an unauthenticated attacker can exploit CVE-2024-9596 to determine the GitLab version number.
Is there a workaround for CVE-2024-9596?
No specific workarounds are provided for CVE-2024-9596; upgrading is the recommended solution.