CVE-2022-4205
First published: Fri Jan 27 2023(Updated: )
In Gitlab EE/CE before 15.6.1, 15.5.5 and 15.4.6 using a branch with a hexadecimal name could override an existing hash.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=1.0.0<12.9.8 | |
| GitLab | >=1.0.0<12.9.8 | |
| GitLab | >=15.5.0<15.5.5 | |
| GitLab | >=15.5.0<15.5.5 | |
| GitLab | =15.6.0 | |
| GitLab | =15.6.0 |
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-2022-4205?
CVE-2022-4205 is considered a critical vulnerability in GitLab affecting specific versions.
How do I fix CVE-2022-4205?
To fix CVE-2022-4205, you should update GitLab to at least version 15.6.1, 15.5.5, or 15.4.6.
Which GitLab versions are affected by CVE-2022-4205?
CVE-2022-4205 affects GitLab versions prior to 15.6.1, 15.5.5, and 15.4.6.
What type of vulnerability is CVE-2022-4205?
CVE-2022-4205 is a security vulnerability that allows a branch with a hexadecimal name to override an existing hash.
Can I still use GitLab if I have CVE-2022-4205?
Using an affected version of GitLab with CVE-2022-4205 poses security risks, so it is recommended to upgrade to a secure version.
- agent/references
- agent/type
- agent/author
- agent/weakness
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/1.0.0
- version/gitlab/15.5.0
- version/gitlab/15.6.0