What is the severity of CVE-2024-5067?

CVE-2024-5067 is considered a medium severity vulnerability due to the potential for disclosure of sensitive project-level analytics.

How do I fix CVE-2024-5067?

To fix CVE-2024-5067, upgrade GitLab to version 17.0.5 or later, 17.1.3 or later, or 17.2.1 or later.

Who is affected by CVE-2024-5067?

CVE-2024-5067 affects all users of GitLab EE versions from 16.11 up to but not including 17.0.5, from 17.1 up to but not including 17.1.3, and from 17.2 up to but not including 17.2.1.

What are the potential impacts of CVE-2024-5067?

The potential impacts of CVE-2024-5067 include unauthorized access to leaked project-level analytics settings by group members with Developer or higher roles.

Is CVE-2024-5067 exploitable remotely?

Yes, CVE-2024-5067 can be exploited remotely by users with the appropriate access levels within GitLab.

Vulnerability/
CVE-2024-5067

medium

4.9

CWE

200

24/7/2024

5/9/2024

CVE-2024-5067: Exposure of Sensitive Information to an Unauthorized Actor in GitLab

First published: Wed Jul 24 2024(Updated: )

An issue was discovered in GitLab EE affecting all versions starting from 16.11 prior to 17.0.5, starting from 17.1 prior to 17.1.3, and starting from 17.2 prior to 17.2.1 where certain project-level analytics settings could be leaked in DOM to group members with Developer or higher roles.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=16.11<17.0.5
GitLab	>=17.1<17.1.3
GitLab	>=17.2<17.2.1

Remedy

Upgrade to versions 17.0.5, 17.1.3, 17.2.1 or above.

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2024-5067?
CVE-2024-5067 is considered a medium severity vulnerability due to the potential for disclosure of sensitive project-level analytics.
How do I fix CVE-2024-5067?
To fix CVE-2024-5067, upgrade GitLab to version 17.0.5 or later, 17.1.3 or later, or 17.2.1 or later.
Who is affected by CVE-2024-5067?
CVE-2024-5067 affects all users of GitLab EE versions from 16.11 up to but not including 17.0.5, from 17.1 up to but not including 17.1.3, and from 17.2 up to but not including 17.2.1.
What are the potential impacts of CVE-2024-5067?
The potential impacts of CVE-2024-5067 include unauthorized access to leaked project-level analytics settings by group members with Developer or higher roles.
Is CVE-2024-5067 exploitable remotely?
Yes, CVE-2024-5067 can be exploited remotely by users with the appropriate access levels within GitLab.

agent/remedy
agent/title
agent/references
agent/weakness
agent/first-publish-date
agent/type
agent/description
agent/author
agent/event
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/softwarecombine
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/16.11
version/gitlab/17.1
version/gitlab/17.2

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.