What is the severity of CVE-2022-0283?

CVE-2022-0283 is classified as a high severity open redirect vulnerability.

How do I fix CVE-2022-0283?

To fix CVE-2022-0283, upgrade your GitLab installation to version 13.5 or later.

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

CVE-2022-0283 affects GitLab versions prior to 13.5 and specific later versions until 14.6.4.

What is the impact of CVE-2022-0283?

The impact of CVE-2022-0283 can lead to unauthorized redirection of users to attacker-controlled websites.

Is it safe to use GitLab versions prior to 13.5 after CVE-2022-0283?

Using GitLab versions prior to 13.5 is not safe due to the potential for exploitation of CVE-2022-0283.

Vulnerability/
CVE-2022-0283

medium

6.1

CWE

601

28/3/2022

2/8/2024

CVE-2022-0283

First published: Mon Mar 28 2022(Updated: )

An issue has been discovered affecting GitLab versions prior to 13.5. An open redirect vulnerability was fixed in GitLab integration with Jira that a could cause the web application to redirect the request to the attacker specified URL.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.5<14.5.4
GitLab	>=14.6<14.6.4
GitLab	=14.7

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-0283?
CVE-2022-0283 is classified as a high severity open redirect vulnerability.
How do I fix CVE-2022-0283?
To fix CVE-2022-0283, upgrade your GitLab installation to version 13.5 or later.
Which versions of GitLab are affected by CVE-2022-0283?
CVE-2022-0283 affects GitLab versions prior to 13.5 and specific later versions until 14.6.4.
What is the impact of CVE-2022-0283?
The impact of CVE-2022-0283 can lead to unauthorized redirection of users to attacker-controlled websites.
Is it safe to use GitLab versions prior to 13.5 after CVE-2022-0283?
Using GitLab versions prior to 13.5 is not safe due to the potential for exploitation of CVE-2022-0283.

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

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-0283?
CVE-2022-0283 is classified as a high severity open redirect vulnerability.
How do I fix CVE-2022-0283?
To fix CVE-2022-0283, upgrade your GitLab installation to version 13.5 or later.
Which versions of GitLab are affected by CVE-2022-0283?
CVE-2022-0283 affects GitLab versions prior to 13.5 and specific later versions until 14.6.4.
What is the impact of CVE-2022-0283?
The impact of CVE-2022-0283 can lead to unauthorized redirection of users to attacker-controlled websites.
Is it safe to use GitLab versions prior to 13.5 after CVE-2022-0283?
Using GitLab versions prior to 13.5 is not safe due to the potential for exploitation of CVE-2022-0283.