What is the severity of CVE-2022-3478?

CVE-2022-3478 is classified as a critical severity vulnerability due to its potential to trigger a denial-of-service (DoS) attack.

How do I fix CVE-2022-3478?

To mitigate CVE-2022-3478, upgrade GitLab to version 15.4.6 or higher, 15.5.5 or higher, or 15.6.1 or higher.

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

CVE-2022-3478 affects GitLab versions from 12.8 to below 15.4.6, from 15.5 to below 15.5.5, and from 15.6 to below 15.6.1.

What type of attack does CVE-2022-3478 enable?

CVE-2022-3478 enables an attacker to conduct a denial-of-service (DoS) attack through the uploading of a malicious nuget package.

Is there a workaround for CVE-2022-3478?

Currently, there is no known workaround for CVE-2022-3478, and users are advised to promptly upgrade to the fixed versions.

Vulnerability/
CVE-2022-3478

medium

4.3

CWE

434

24/1/2023

3/8/2024

CVE-2022-3478: Malicious File Upload

First published: Tue Jan 24 2023(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 12.8 before 15.4.6, all versions starting from 15.5 before 15.5.5, all versions starting from 15.6 before 15.6.1. It was possible to trigger a DoS attack by uploading a malicious nuget package.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.8.0<15.4.6
GitLab	>=12.8.0<15.4.6
GitLab	>=15.5.0<15.5.5
GitLab	>=15.5.0<15.5.5
GitLab	=15.6.0
GitLab	=15.6.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-3478?
CVE-2022-3478 is classified as a critical severity vulnerability due to its potential to trigger a denial-of-service (DoS) attack.
How do I fix CVE-2022-3478?
To mitigate CVE-2022-3478, upgrade GitLab to version 15.4.6 or higher, 15.5.5 or higher, or 15.6.1 or higher.
What versions of GitLab are affected by CVE-2022-3478?
CVE-2022-3478 affects GitLab versions from 12.8 to below 15.4.6, from 15.5 to below 15.5.5, and from 15.6 to below 15.6.1.
What type of attack does CVE-2022-3478 enable?
CVE-2022-3478 enables an attacker to conduct a denial-of-service (DoS) attack through the uploading of a malicious nuget package.
Is there a workaround for CVE-2022-3478?
Currently, there is no known workaround for CVE-2022-3478, and users are advised to promptly upgrade to the fixed versions.

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/12.8.0
version/gitlab/15.5.0
version/gitlab/15.6.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-3478?
CVE-2022-3478 is classified as a critical severity vulnerability due to its potential to trigger a denial-of-service (DoS) attack.
How do I fix CVE-2022-3478?
To mitigate CVE-2022-3478, upgrade GitLab to version 15.4.6 or higher, 15.5.5 or higher, or 15.6.1 or higher.
What versions of GitLab are affected by CVE-2022-3478?
CVE-2022-3478 affects GitLab versions from 12.8 to below 15.4.6, from 15.5 to below 15.5.5, and from 15.6 to below 15.6.1.
What type of attack does CVE-2022-3478 enable?
CVE-2022-3478 enables an attacker to conduct a denial-of-service (DoS) attack through the uploading of a malicious nuget package.
Is there a workaround for CVE-2022-3478?
Currently, there is no known workaround for CVE-2022-3478, and users are advised to promptly upgrade to the fixed versions.