CVE-2023-6840: Missing Authorization in GitLab
First published: Wed Feb 07 2024(Updated: )
An issue has been discovered in GitLab EE affecting all versions from 16.4 prior to 16.6.7, 16.7 prior to 16.7.5, and 16.8 prior to 16.8.2 which allows a maintainer to change the name of a protected branch that bypasses the security policy added to block MR.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=16.4.0<16.6.7 | |
| GitLab | >=16.7.0<16.7.5 | |
| GitLab | >=16.8.0<16.8.2 |
Remedy
Upgrade to versions 16.8.2, 16.7.5, 16.6.7 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-2023-6840?
CVE-2023-6840 is classified as a medium severity vulnerability.
What versions of GitLab EE are affected by CVE-2023-6840?
CVE-2023-6840 affects GitLab EE versions from 16.4 prior to 16.6.7, 16.7 prior to 16.7.5, and 16.8 prior to 16.8.2.
How do I fix CVE-2023-6840?
To fix CVE-2023-6840, upgrade to GitLab EE versions 16.6.7, 16.7.5, or 16.8.2 or newer.
What is the impact of CVE-2023-6840?
CVE-2023-6840 allows a maintainer to change the name of a protected branch, bypassing existing security policies.
Who can exploit CVE-2023-6840?
CVE-2023-6840 can be exploited by any maintainer with access to the protected branch in the affected GitLab EE versions.
- agent/remedy
- agent/references
- agent/description
- agent/type
- agent/first-publish-date
- agent/severity
- agent/author
- agent/event
- agent/softwarecombine
- agent/title
- agent/weakness
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- 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.4.0
- version/gitlab/16.7.0
- version/gitlab/16.8.0