First published: Mon Oct 17 2022(Updated: )
An issue has been discovered in GitLab affecting all versions starting from 12.10 before 15.1.6, all versions starting from 15.2 before 15.2.4, all versions starting from 15.3 before 15.3.2. GitLab was not performing correct authentication with some Package Registries when IP address restrictions were configured, allowing an attacker already in possession of a valid Deploy Token to misuse it from any location.
Credit: cve@gitlab.com
Affected Software | Affected Version | How to fix |
---|---|---|
GitLab | >=12.10<15.1.6 | |
GitLab | >=12.10<15.1.6 | |
GitLab | >=15.2<15.2.4 | |
GitLab | >=15.2<15.2.4 | |
GitLab | >=15.3<15.3.2 | |
GitLab | >=15.3<15.3.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-2533 has been classified as a high severity vulnerability due to authentication flaws in GitLab.
To fix CVE-2022-2533, upgrade your GitLab instance to version 15.1.6, 15.2.4, or 15.3.2 or later.
CVE-2022-2533 affects GitLab versions from 12.10 to 15.1.6, from 15.2 to 15.2.4, and from 15.3 to 15.3.2.
CVE-2022-2533 is an authentication vulnerability that allows for improper access control in GitLab package registries.
There are no recommended workarounds for CVE-2022-2533; the best approach is to upgrade to the patched versions promptly.