What is the severity of CVE-2021-22197?

CVE-2021-22197 is classified as a critical vulnerability due to the potential denial of service through an infinite loop.

How does CVE-2021-22197 affect GitLab users?

CVE-2021-22197 affects authenticated users with specific rights when accessing merge requests that have source and target branches pointing to each other.

Which versions of GitLab are impacted by CVE-2021-22197?

CVE-2021-22197 affects all GitLab versions starting from 10.6 up to and including 13.10.1.

How do I fix CVE-2021-22197?

To fix CVE-2021-22197, users should upgrade to a patched version of GitLab, specifically 13.10.1 or later.

What should I do if I cannot upgrade GitLab to mitigate CVE-2021-22197?

If upgrading is not possible, it is recommended to restrict access rights for users who can access merge requests until you can apply the necessary updates.

Vulnerability/
CVE-2021-22197

medium

4.3

CWE

835

2/4/2021

21/8/2024

CVE-2021-22197

First published: Fri Apr 02 2021(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions starting from 10.6 where an infinite loop exist when an authenticated user with specific rights access a MR having source and target branch pointing to each other

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

Affected Software	Affected Version	How to fix
GitLab	>=10.6.0<13.8.7
GitLab	>=10.6.0<13.8.7
GitLab	>=13.9.0<13.9.5
GitLab	>=13.9.0<13.9.5
GitLab	>=13.10.0<13.10.1
GitLab	>=13.10.0<13.10.1
GitLab	>=10.6.0
GitLab	>=10.6.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-22197?
CVE-2021-22197 is classified as a critical vulnerability due to the potential denial of service through an infinite loop.
How does CVE-2021-22197 affect GitLab users?
CVE-2021-22197 affects authenticated users with specific rights when accessing merge requests that have source and target branches pointing to each other.
Which versions of GitLab are impacted by CVE-2021-22197?
CVE-2021-22197 affects all GitLab versions starting from 10.6 up to and including 13.10.1.
How do I fix CVE-2021-22197?
To fix CVE-2021-22197, users should upgrade to a patched version of GitLab, specifically 13.10.1 or later.
What should I do if I cannot upgrade GitLab to mitigate CVE-2021-22197?
If upgrading is not possible, it is recommended to restrict access rights for users who can access merge requests until you can apply the necessary updates.

agent/type
agent/references
agent/weakness
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/first-publish-date
agent/event
agent/author
agent/last-modified-date
agent/softwarecombine
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
collector/nvd-index
vendor/gitlab
canonical/gitlab
version/gitlab/10.6.0
version/gitlab/13.9.0
version/gitlab/13.10.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-2021-22197?
CVE-2021-22197 is classified as a critical vulnerability due to the potential denial of service through an infinite loop.
How does CVE-2021-22197 affect GitLab users?
CVE-2021-22197 affects authenticated users with specific rights when accessing merge requests that have source and target branches pointing to each other.
Which versions of GitLab are impacted by CVE-2021-22197?
CVE-2021-22197 affects all GitLab versions starting from 10.6 up to and including 13.10.1.
How do I fix CVE-2021-22197?
To fix CVE-2021-22197, users should upgrade to a patched version of GitLab, specifically 13.10.1 or later.
What should I do if I cannot upgrade GitLab to mitigate CVE-2021-22197?
If upgrading is not possible, it is recommended to restrict access rights for users who can access merge requests until you can apply the necessary updates.