CVE-2024-7060 Exposure of Sensitive Information to an Unauthorized Actor in GitLab
Unauthorized users can view sensitive information from project or group exports in GitLab, requiring an upgrade to secure the data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2024-7060?
CVE-2024-7060 is a low-severity vulnerability in Gitlab Gitlab, published on 24 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
An information disclosure vulnerability in GitLab CE/EE in project/group exports affecting all versions from 15.4 prior to 17.0.5, 17.1 prior to 17.1.3, and 17.2 prior to 17.2.1 allows unauthorized users to view the resultant export.
Weakness: CWE-200
Which versions are affected by CVE-2024-7060?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 15.4.0 | 17.0.5, 17.1.3, 17.2.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2024-7060?
Upgrade gitlab to a fixed version for your release line: 17.0.5, 17.1.3 or 17.2.1.
Is CVE-2024-7060 being exploited?
There is no known exploitation of CVE-2024-7060 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2024-7060, GHSA-pqgh-rchr-9hg3.