What is the severity of CVE-2022-3818?

CVE-2022-3818 has been classified as a high severity vulnerability due to its potential to cause denial of service on affected GitLab instances.

How do I fix CVE-2022-3818?

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

Is CVE-2022-3818 applicable to both GitLab CE and EE?

Yes, CVE-2022-3818 affects both GitLab Community Edition (CE) and Enterprise Edition (EE) versions prior to the specified updates.

Vulnerability/
CVE-2022-3818

medium

5.3

CWE

400

9/11/2022

3/8/2024

CVE-2022-3818

Q: What versions are affected by CVE-2022-3818?

All GitLab CE/EE versions prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 are affected by CVE-2022-3818.

Q: What types of issues does CVE-2022-3818 cause?

CVE-2022-3818 can lead to performance issues and potentially a denial of service condition on GitLab instances.

First published: Wed Nov 09 2022(Updated: )

An uncontrolled resource consumption issue when parsing URLs in GitLab CE/EE affecting all versions prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows an attacker to cause performance issues and potentially a denial of service on the GitLab instance.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<15.3.5
GitLab	<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-3818?
CVE-2022-3818 has been classified as a high severity vulnerability due to its potential to cause denial of service on affected GitLab instances.
How do I fix CVE-2022-3818?
To fix CVE-2022-3818, upgrade your GitLab instance to version 15.3.5, 15.4.4, or 15.5.2 or later.
What versions are affected by CVE-2022-3818?
All GitLab CE/EE versions prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 are affected by CVE-2022-3818.
What types of issues does CVE-2022-3818 cause?
CVE-2022-3818 can lead to performance issues and potentially a denial of service condition on GitLab instances.
Is CVE-2022-3818 applicable to both GitLab CE and EE?
Yes, CVE-2022-3818 affects both GitLab Community Edition (CE) and Enterprise Edition (EE) versions prior to the specified updates.

agent/type
agent/references
agent/author
agent/weakness
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
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-3818?
CVE-2022-3818 has been classified as a high severity vulnerability due to its potential to cause denial of service on affected GitLab instances.
How do I fix CVE-2022-3818?
To fix CVE-2022-3818, upgrade your GitLab instance to version 15.3.5, 15.4.4, or 15.5.2 or later.
What versions are affected by CVE-2022-3818?
All GitLab CE/EE versions prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 are affected by CVE-2022-3818.
What types of issues does CVE-2022-3818 cause?
CVE-2022-3818 can lead to performance issues and potentially a denial of service condition on GitLab instances.
Is CVE-2022-3818 applicable to both GitLab CE and EE?
Yes, CVE-2022-3818 affects both GitLab Community Edition (CE) and Enterprise Edition (EE) versions prior to the specified updates.