First published: Mon Oct 17 2022(Updated: )
A branch/tag name confusion in GitLab CE/EE affecting all versions prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1 allows an attacker to manipulate pages where the content of the default branch would be expected.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | <15.2.5 | |
GitLab | <15.2.5 | |
GitLab | >=15.3<15.3.4 | |
GitLab | >=15.3<15.3.4 | |
GitLab | >=15.4<15.4.1 | |
GitLab | >=15.4<15.4.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-3288 is considered a medium severity vulnerability due to its potential to manipulate content based on branch confusion.
To fix CVE-2022-3288, users should upgrade to GitLab versions 15.2.5, 15.3.4, or 15.4.1 and later.
CVE-2022-3288 affects all versions of GitLab CE and EE prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1.
CVE-2022-3288 allows an attacker to manipulate pages where the content of the default branch would be expected.
No, CVE-2022-3288 has been addressed and is not present in GitLab versions 15.2.5, 15.3.4, or 15.4.1 and later.