What is the severity of CVE-2022-3486?

The severity of CVE-2022-3486 is considered high due to the potential for exploitation via open redirects.

How do I fix CVE-2022-3486?

To fix CVE-2022-3486, update your GitLab instance to version 15.3.5, 15.4.4, or 15.5.2 or later.

What versions of GitLab are affected by CVE-2022-3486?

CVE-2022-3486 affects all GitLab EE/CE versions from 9.3 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2.

What are the potential impacts of CVE-2022-3486?

The potential impacts of CVE-2022-3486 include enabling attackers to redirect users to malicious sites through trusted URLs.

Is CVE-2022-3486 exploitable without authentication?

Yes, CVE-2022-3486 can be exploited without user authentication, making it particularly concerning.

Vulnerability/
CVE-2022-3486

medium

6.1

CWE

601

9/11/2022

3/8/2024

CVE-2022-3486

First published: Wed Nov 09 2022(Updated: )

An open redirect vulnerability in GitLab EE/CE affecting all versions from 9.3 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2, allows an attacker to redirect users to an arbitrary location if they trust the URL.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=9.4.0<15.3.5
GitLab	>=9.4.0<15.3.5
GitLab	>=15.4.0<15.4.4
GitLab	>=15.4.0<15.4.4
GitLab	>=15.5.0<15.5.2
GitLab	>=15.5.0<15.5.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-3486?
The severity of CVE-2022-3486 is considered high due to the potential for exploitation via open redirects.
How do I fix CVE-2022-3486?
To fix CVE-2022-3486, update your GitLab instance to version 15.3.5, 15.4.4, or 15.5.2 or later.
What versions of GitLab are affected by CVE-2022-3486?
CVE-2022-3486 affects all GitLab EE/CE versions from 9.3 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2.
What are the potential impacts of CVE-2022-3486?
The potential impacts of CVE-2022-3486 include enabling attackers to redirect users to malicious sites through trusted URLs.
Is CVE-2022-3486 exploitable without authentication?
Yes, CVE-2022-3486 can be exploited without user authentication, making it particularly concerning.

agent/type
agent/references
agent/author
agent/weakness
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/9.4.0
version/gitlab/15.4.0
version/gitlab/15.5.0

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-3486?
The severity of CVE-2022-3486 is considered high due to the potential for exploitation via open redirects.
How do I fix CVE-2022-3486?
To fix CVE-2022-3486, update your GitLab instance to version 15.3.5, 15.4.4, or 15.5.2 or later.
What versions of GitLab are affected by CVE-2022-3486?
CVE-2022-3486 affects all GitLab EE/CE versions from 9.3 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2.
What are the potential impacts of CVE-2022-3486?
The potential impacts of CVE-2022-3486 include enabling attackers to redirect users to malicious sites through trusted URLs.
Is CVE-2022-3486 exploitable without authentication?
Yes, CVE-2022-3486 can be exploited without user authentication, making it particularly concerning.