What is the severity of CVE-2022-1100?

CVE-2022-1100 is classified as a potential denial-of-service (DoS) vulnerability in GitLab.

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

CVE-2022-1100 affects all versions of GitLab from 13.1 prior to 14.7.7, 14.8.0 prior to 14.8.5, and 14.9.0 prior to 14.9.2.

How do I fix CVE-2022-1100?

To mitigate CVE-2022-1100, upgrade to GitLab versions 14.7.7, 14.8.5, or 14.9.2 or later.

What type of vulnerability is CVE-2022-1100?

CVE-2022-1100 is identified as a regular expression (regex) denial-of-service vulnerability.

Can CVE-2022-1100 be exploited remotely?

Yes, CVE-2022-1100 can potentially be exploited remotely if the vulnerable versions of GitLab are accessible.

Vulnerability/
CVE-2022-1100

medium

4.3

CWE

772 20

4/4/2022

2/8/2024

CVE-2022-1100: Input Validation

First published: Mon Apr 04 2022(Updated: )

A potential DOS vulnerability was discovered in GitLab CE/EE affecting all versions from 13.1 prior to 14.7.7, 14.8.0 prior to 14.8.5, and 14.9.0 prior to 14.9.2. The api to update an asset as a link from a release had a regex check which caused exponential number of backtracks for certain user supplied values resulting in high CPU usage.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.1.0<14.7.7
GitLab	>=13.1.0<14.7.7
GitLab	>=14.8.0<14.8.5
GitLab	>=14.8.0<14.8.5
GitLab	>=14.9.0<14.9.2
GitLab	>=14.9.0<14.9.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-1100?
CVE-2022-1100 is classified as a potential denial-of-service (DoS) vulnerability in GitLab.
What versions of GitLab are affected by CVE-2022-1100?
CVE-2022-1100 affects all versions of GitLab from 13.1 prior to 14.7.7, 14.8.0 prior to 14.8.5, and 14.9.0 prior to 14.9.2.
How do I fix CVE-2022-1100?
To mitigate CVE-2022-1100, upgrade to GitLab versions 14.7.7, 14.8.5, or 14.9.2 or later.
What type of vulnerability is CVE-2022-1100?
CVE-2022-1100 is identified as a regular expression (regex) denial-of-service vulnerability.
Can CVE-2022-1100 be exploited remotely?
Yes, CVE-2022-1100 can potentially be exploited remotely if the vulnerable versions of GitLab are accessible.

agent/references
agent/type
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/weakness
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/13.1.0
version/gitlab/14.8.0
version/gitlab/14.9.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-1100?
CVE-2022-1100 is classified as a potential denial-of-service (DoS) vulnerability in GitLab.
What versions of GitLab are affected by CVE-2022-1100?
CVE-2022-1100 affects all versions of GitLab from 13.1 prior to 14.7.7, 14.8.0 prior to 14.8.5, and 14.9.0 prior to 14.9.2.
How do I fix CVE-2022-1100?
To mitigate CVE-2022-1100, upgrade to GitLab versions 14.7.7, 14.8.5, or 14.9.2 or later.
What type of vulnerability is CVE-2022-1100?
CVE-2022-1100 is identified as a regular expression (regex) denial-of-service vulnerability.
Can CVE-2022-1100 be exploited remotely?
Yes, CVE-2022-1100 can potentially be exploited remotely if the vulnerable versions of GitLab are accessible.