What is the severity of CVE-2022-2417?

CVE-2022-2417 has been classified as a medium severity vulnerability due to insufficient validation.

How do I fix CVE-2022-2417?

To fix CVE-2022-2417, upgrade your GitLab installation to version 15.0.5 or later, 15.1.4 or later, or 15.2.1 or later.

Who is affected by CVE-2022-2417?

CVE-2022-2417 affects all versions of GitLab CE/EE from 12.10 up to versions prior to 15.0.5, 15.1.4, and 15.2.1.

What type of attack can exploit CVE-2022-2417?

An authenticated user can exploit CVE-2022-2417 to import a project with malicious branch names, potentially causing supply chain issues.

Is there a workaround for CVE-2022-2417 until I can update?

There are no recommended workarounds for CVE-2022-2417, so updating to a patched version is essential for security.

Vulnerability/
CVE-2022-2417

medium

6.2

CWE

5/8/2022

3/8/2024

CVE-2022-2417: Input Validation

First published: Fri Aug 05 2022(Updated: )

Insufficient validation in GitLab CE/EE affecting all versions from 12.10 prior to 15.0.5, 15.1 prior to 15.1.4, and 15.2 prior to 15.2.1 allows an authenticated and authorised user to import a project that includes branch names which are 40 hexadecimal characters, which could be abused in supply chain attacks where a victim pinned to a specific Git commit of the project.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.10.0<15.0.5
GitLab	>=15.1.0<15.1.4
GitLab	=15.2
GitLab	>=12.10.0<15.0.5
GitLab	>=15.1.0<15.1.4
GitLab	=15.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-2417?
CVE-2022-2417 has been classified as a medium severity vulnerability due to insufficient validation.
How do I fix CVE-2022-2417?
To fix CVE-2022-2417, upgrade your GitLab installation to version 15.0.5 or later, 15.1.4 or later, or 15.2.1 or later.
Who is affected by CVE-2022-2417?
CVE-2022-2417 affects all versions of GitLab CE/EE from 12.10 up to versions prior to 15.0.5, 15.1.4, and 15.2.1.
What type of attack can exploit CVE-2022-2417?
An authenticated user can exploit CVE-2022-2417 to import a project with malicious branch names, potentially causing supply chain issues.
Is there a workaround for CVE-2022-2417 until I can update?
There are no recommended workarounds for CVE-2022-2417, so updating to a patched version is essential for security.

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/12.10.0
version/gitlab/15.1.0
version/gitlab/15.2

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-2417?
CVE-2022-2417 has been classified as a medium severity vulnerability due to insufficient validation.
How do I fix CVE-2022-2417?
To fix CVE-2022-2417, upgrade your GitLab installation to version 15.0.5 or later, 15.1.4 or later, or 15.2.1 or later.
Who is affected by CVE-2022-2417?
CVE-2022-2417 affects all versions of GitLab CE/EE from 12.10 up to versions prior to 15.0.5, 15.1.4, and 15.2.1.
What type of attack can exploit CVE-2022-2417?
An authenticated user can exploit CVE-2022-2417 to import a project with malicious branch names, potentially causing supply chain issues.
Is there a workaround for CVE-2022-2417 until I can update?
There are no recommended workarounds for CVE-2022-2417, so updating to a patched version is essential for security.