published 10 Oct 2024 · updated 10 Oct 2024
Inclusion of Sensitive Information in Source Code in GitLab
3.7LowCVSS 3.7EPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in GitLab 17.2.9, GitLab 17.3.5 and GitLab 17.4.2.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| GitLab | GitLab | >=16.6 <17.2.9, >=17.3 <17.3.5, >=17.4 <17.4.2 | 17.2.9, 17.3.5, 17.4.2 |
Exploit evidence
1 public sources
Vendor advisories
Timeline
Every event on this vulnerability
Vendor advisoryCVE-2024-9596·
3.7Low
Related
Other vulnerabilities in GitLab, strongest first
10.0CriticalPublic exploit
10.0CriticalCISA KEVPublic exploit
10.0CriticalPublic exploit
10.0CriticalPublic exploit
10.0CriticalCISA KEVPublic exploit
10.0CriticalPublic exploit
Embed
A live severity badge for an advisory, README or ticket