CVE-2022-4205: High severity gitlab vulnerability
Published 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.
Affected Software
6 affected components
GitLab GitLab>=1.0.0<12.9.8
GitLab GitLab>=1.0.0<12.9.8
GitLab GitLab>=15.5.0<15.5.5
GitLab GitLab>=15.5.0<15.5.5
GitLab GitLab=15.6.0
GitLab GitLab=15.6.0
Event History
Jan 27, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2022-4205?
CVE-2022-4205 is considered a critical vulnerability in GitLab affecting specific versions.
2
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.
3
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.
4
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.
5
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.