What is the severity of CVE-2022-3286?

CVE-2022-3286 is categorized as a high-severity vulnerability due to its potential to bypass IP address restrictions in GitLab EE.

How do I fix CVE-2022-3286?

To fix CVE-2022-3286, upgrade GitLab EE to version 15.2.5, 15.3.4, or 15.4.1 or later.

Which versions of GitLab are affected by CVE-2022-3286?

CVE-2022-3286 affects GitLab EE versions from 14.2 prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1.

What is the impact of CVE-2022-3286?

The impact of CVE-2022-3286 allows unauthorized group members to bypass established IP address restrictions using a deploy token.

Is user authentication affected by CVE-2022-3286?

CVE-2022-3286 does not directly affect user authentication but allows bypassing IP restrictions, potentially compromising security.

Vulnerability/
CVE-2022-3286

medium

5.3

17/10/2022

3/8/2024

CVE-2022-3286

First published: Mon Oct 17 2022(Updated: )

Lack of IP address checking in GitLab EE affecting all versions from 14.2 prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1 allows a group member to bypass IP restrictions when using a deploy token

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=14.2<15.2.5
GitLab	>=15.3<15.3.4
GitLab	>=15.4<15.4.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-3286?
CVE-2022-3286 is categorized as a high-severity vulnerability due to its potential to bypass IP address restrictions in GitLab EE.
How do I fix CVE-2022-3286?
To fix CVE-2022-3286, upgrade GitLab EE to version 15.2.5, 15.3.4, or 15.4.1 or later.
Which versions of GitLab are affected by CVE-2022-3286?
CVE-2022-3286 affects GitLab EE versions from 14.2 prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1.
What is the impact of CVE-2022-3286?
The impact of CVE-2022-3286 allows unauthorized group members to bypass established IP address restrictions using a deploy token.
Is user authentication affected by CVE-2022-3286?
CVE-2022-3286 does not directly affect user authentication but allows bypassing IP restrictions, potentially compromising security.

agent/references
agent/type
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/14.2
version/gitlab/15.3
version/gitlab/15.4

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-3286?
CVE-2022-3286 is categorized as a high-severity vulnerability due to its potential to bypass IP address restrictions in GitLab EE.
How do I fix CVE-2022-3286?
To fix CVE-2022-3286, upgrade GitLab EE to version 15.2.5, 15.3.4, or 15.4.1 or later.
Which versions of GitLab are affected by CVE-2022-3286?
CVE-2022-3286 affects GitLab EE versions from 14.2 prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1.
What is the impact of CVE-2022-3286?
The impact of CVE-2022-3286 allows unauthorized group members to bypass established IP address restrictions using a deploy token.
Is user authentication affected by CVE-2022-3286?
CVE-2022-3286 does not directly affect user authentication but allows bypassing IP restrictions, potentially compromising security.