CVE-2024-9596

Inclusion of Sensitive Information in Source Code in GitLab

Description

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.

Remediation

Solution:

  • Upgrade to version 17.2.9, 17.3.5 or 17.4.2

Category

3.7
CVSS
Severity: Low
CVSS 3.1 •
EPSS 0.02%
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/493355 broken link issue tracking permissions required

Frequently Asked Questions

What is the severity of CVE-2024-9596?
CVE-2024-9596 has been scored as a low severity vulnerability.
How to fix CVE-2024-9596?
To fix CVE-2024-9596: Upgrade to version 17.2.9, 17.3.5 or 17.4.2
Is CVE-2024-9596 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2024-9596 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2024-9596?
CVE-2024-9596 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.