First published: Fri Dec 15 2023(Updated: )
An issue has been discovered in GitLab CE/EE affecting all versions before 16.4.4, all versions starting from 16.5 before 16.5.4, all versions starting from 16.6 before 16.6.2. File integrity may be compromised when source code or installation packages are pulled from a specific tag.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | <16.4.4 | |
GitLab | <16.4.4 | |
GitLab | >=16.5.0<16.5.4 | |
GitLab | >=16.5.0<16.5.4 |
Upgrade to versions 16.6.2, 16.5.4, 16.4.4 or above.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-6051 has a severity level that indicates a significant risk to file integrity in vulnerable GitLab versions.
To fix CVE-2023-6051, upgrade to GitLab version 16.4.4, 16.5.4, or 16.6.2 or later.
CVE-2023-6051 affects all GitLab CE/EE versions prior to 16.4.4 and certain versions from 16.5.0 to 16.5.4 and from 16.6.0 to 16.6.2.
Exploitation of CVE-2023-6051 could allow attackers to compromise the integrity of source code or installation packages.
Yes, you can use GitLab CE or EE only if you have upgraded to a version that is not affected by CVE-2023-6051.