CVE-2024-10925: Authorization Bypass Through User-Controlled Key in GitLab
First published: Mon Mar 03 2025(Updated: )
A vulnerability in GitLab-EE affecting all versions from 16.2 prior to 17.7.6, 17.8 prior to 17.8.4, and 17.9 prior to 17.9.1 allows a Guest user to read Security policy YAML
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=16.2<17.7.6>=17.8<17.8.4>=17.9<17.9.1 |
Remedy
Upgrade to versions 17.7.6, 17.8.4, 17.9.1 or above.
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-10925?
CVE-2024-10925 is classified as a medium severity vulnerability.
Who is affected by CVE-2024-10925?
CVE-2024-10925 affects GitLab-EE versions from 16.2 prior to 17.7.6, 17.8 prior to 17.8.4, and 17.9 prior to 17.9.1.
How do I fix CVE-2024-10925?
To fix CVE-2024-10925, you should upgrade to GitLab-EE version 17.7.6, 17.8.4, or 17.9.1 or later.
What type of access does CVE-2024-10925 grant to attackers?
CVE-2024-10925 allows a Guest user to read sensitive Security policy YAML files.
What potential impact does CVE-2024-10925 have on my GitLab instance?
CVE-2024-10925 could lead to exposure of sensitive security information to unauthorized users.
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/title
- agent/remedy
- agent/references
- agent/type
- agent/first-publish-date
- agent/description
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/severity
- agent/author
- agent/last-modified-date
- agent/source
- agent/tags
- agent/event
- vendor/gitlab
- canonical/gitlab