What is the severity of CVE-2022-4131?

CVE-2022-4131 has been classified as a Denial of Service vulnerability.

How do I fix CVE-2022-4131?

To fix CVE-2022-4131, upgrade GitLab to version 15.5.7 or later, 15.6.4 or later, or 15.7.2 or later.

What versions are affected by CVE-2022-4131?

CVE-2022-4131 affects GitLab CE/EE versions from 10.8 to 15.5.7 and from 15.6 to 15.6.4 and from 15.7 to 15.7.2.

Can CVE-2022-4131 be exploited remotely?

Yes, CVE-2022-4131 can be exploited remotely, potentially leading to a Denial of Service.

Is there a workaround for CVE-2022-4131?

There are no known workarounds for CVE-2022-4131; updating to a patched version is recommended.

Vulnerability/
CVE-2022-4131

medium

5.3

CWE

1333

12/1/2023

3/8/2024

CVE-2022-4131

First published: Thu Jan 12 2023(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions starting from 10.8 before 15.5.7, all versions starting from 15.6 before 15.6.4, all versions starting from 15.7 before 15.7.2. An attacker may cause Denial of Service on a GitLab instance by exploiting a regex issue in how the application parses user agents.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=10.8.0<15.5.7
GitLab	>=10.8.0<15.5.7
GitLab	>=15.6.0<15.6.4
GitLab	>=15.6.0<15.6.4
GitLab	>=15.7.0<15.7.2
GitLab	>=15.7.0<15.7.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-4131?
CVE-2022-4131 has been classified as a Denial of Service vulnerability.
How do I fix CVE-2022-4131?
To fix CVE-2022-4131, upgrade GitLab to version 15.5.7 or later, 15.6.4 or later, or 15.7.2 or later.
What versions are affected by CVE-2022-4131?
CVE-2022-4131 affects GitLab CE/EE versions from 10.8 to 15.5.7 and from 15.6 to 15.6.4 and from 15.7 to 15.7.2.
Can CVE-2022-4131 be exploited remotely?
Yes, CVE-2022-4131 can be exploited remotely, potentially leading to a Denial of Service.
Is there a workaround for CVE-2022-4131?
There are no known workarounds for CVE-2022-4131; updating to a patched version is recommended.

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/10.8.0
version/gitlab/15.6.0
version/gitlab/15.7.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-4131?
CVE-2022-4131 has been classified as a Denial of Service vulnerability.
How do I fix CVE-2022-4131?
To fix CVE-2022-4131, upgrade GitLab to version 15.5.7 or later, 15.6.4 or later, or 15.7.2 or later.
What versions are affected by CVE-2022-4131?
CVE-2022-4131 affects GitLab CE/EE versions from 10.8 to 15.5.7 and from 15.6 to 15.6.4 and from 15.7 to 15.7.2.
Can CVE-2022-4131 be exploited remotely?
Yes, CVE-2022-4131 can be exploited remotely, potentially leading to a Denial of Service.
Is there a workaround for CVE-2022-4131?
There are no known workarounds for CVE-2022-4131; updating to a patched version is recommended.