What is the severity of CVE-2022-1954?

CVE-2022-1954 is classified as a Regular Expression Denial of Service vulnerability.

How do I fix CVE-2022-1954?

To fix CVE-2022-1954, update your GitLab instance to version 14.10.5, 15.0.4, or 15.1.1 or later.

Which versions are affected by CVE-2022-1954?

CVE-2022-1954 affects all versions of GitLab from 1.0.2 prior to 14.10.5, all versions from 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1.

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

Yes, CVE-2022-1954 affects both GitLab Community Edition (CE) and Enterprise Edition (EE) versions.

Vulnerability/
CVE-2022-1954

medium

5.3

CWE

1333

1/7/2022

3/8/2024

CVE-2022-1954

Q: What type of attack does CVE-2022-1954 enable?

CVE-2022-1954 enables an attacker to make a GitLab instance inaccessible via specially crafted web server response headers.

First published: Fri Jul 01 2022(Updated: )

A Regular Expression Denial of Service vulnerability in GitLab CE/EE affecting all versions from 1.0.2 prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 allows an attacker to make a GitLab instance inaccessible via specially crafted web server response headers

Credit: cve@gitlab.com cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=1.0.2<14.10.5
GitLab	>=1.0.2<14.10.5
GitLab	>=15.0.0<15.0.4
GitLab	>=15.0.0<15.0.4
GitLab	=15.1.0
GitLab	=15.1.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-1954?
CVE-2022-1954 is classified as a Regular Expression Denial of Service vulnerability.
How do I fix CVE-2022-1954?
To fix CVE-2022-1954, update your GitLab instance to version 14.10.5, 15.0.4, or 15.1.1 or later.
Which versions are affected by CVE-2022-1954?
CVE-2022-1954 affects all versions of GitLab from 1.0.2 prior to 14.10.5, all versions from 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1.
What type of attack does CVE-2022-1954 enable?
CVE-2022-1954 enables an attacker to make a GitLab instance inaccessible via specially crafted web server response headers.
Is CVE-2022-1954 applicable to both GitLab CE and EE?
Yes, CVE-2022-1954 affects both GitLab Community Edition (CE) and Enterprise Edition (EE) versions.

agent/author
agent/type
agent/references
agent/weakness
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/first-publish-date
agent/event
agent/source
collector/nvd-api
agent/software-canonical-lookup-request
agent/softwarecombine
agent/tags
collector/nvd-index
vendor/gitlab
canonical/gitlab
version/gitlab/1.0.2
version/gitlab/15.0.0
version/gitlab/15.1.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-1954?
CVE-2022-1954 is classified as a Regular Expression Denial of Service vulnerability.
How do I fix CVE-2022-1954?
To fix CVE-2022-1954, update your GitLab instance to version 14.10.5, 15.0.4, or 15.1.1 or later.
Which versions are affected by CVE-2022-1954?
CVE-2022-1954 affects all versions of GitLab from 1.0.2 prior to 14.10.5, all versions from 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1.
What type of attack does CVE-2022-1954 enable?
CVE-2022-1954 enables an attacker to make a GitLab instance inaccessible via specially crafted web server response headers.
Is CVE-2022-1954 applicable to both GitLab CE and EE?
Yes, CVE-2022-1954 affects both GitLab Community Edition (CE) and Enterprise Edition (EE) versions.