What is the severity of CVE-2021-22251?

CVE-2021-22251 is classified as a medium severity vulnerability.

How do I fix CVE-2021-22251?

To resolve CVE-2021-22251, upgrade to GitLab versions 13.12.10, 14.0.8, or 14.1.3 or later.

What are the consequences of CVE-2021-22251?

CVE-2021-22251 may allow unauthorized users to add members to projects using blocked email domains.

Which versions of GitLab are affected by CVE-2021-22251?

CVE-2021-22251 affects GitLab versions from 12.2.0 to 13.12.9, 14.0.0 to 14.0.7, and 14.1.0 to 14.1.2.

Is there a workaround for CVE-2021-22251?

Currently, there is no official workaround for CVE-2021-22251; updating GitLab is recommended.

Vulnerability/
CVE-2021-22251

medium

4.3

CWE

863 20

23/8/2021

3/8/2024

CVE-2021-22251: Input Validation

First published: Mon Aug 23 2021(Updated: )

Improper validation of invited users' email address in GitLab EE affecting all versions since 12.2 allowed projects to add members with email address domain that should be blocked by group settings

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.2.0<13.12.9
GitLab	>=14.0.0<14.0.7
GitLab	>=14.1.0<14.1.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-22251?
CVE-2021-22251 is classified as a medium severity vulnerability.
How do I fix CVE-2021-22251?
To resolve CVE-2021-22251, upgrade to GitLab versions 13.12.10, 14.0.8, or 14.1.3 or later.
What are the consequences of CVE-2021-22251?
CVE-2021-22251 may allow unauthorized users to add members to projects using blocked email domains.
Which versions of GitLab are affected by CVE-2021-22251?
CVE-2021-22251 affects GitLab versions from 12.2.0 to 13.12.9, 14.0.0 to 14.0.7, and 14.1.0 to 14.1.2.
Is there a workaround for CVE-2021-22251?
Currently, there is no official workaround for CVE-2021-22251; updating GitLab is recommended.

agent/type
agent/references
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/weakness
agent/severity
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/12.2.0
version/gitlab/14.0.0
version/gitlab/14.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-2021-22251?
CVE-2021-22251 is classified as a medium severity vulnerability.
How do I fix CVE-2021-22251?
To resolve CVE-2021-22251, upgrade to GitLab versions 13.12.10, 14.0.8, or 14.1.3 or later.
What are the consequences of CVE-2021-22251?
CVE-2021-22251 may allow unauthorized users to add members to projects using blocked email domains.
Which versions of GitLab are affected by CVE-2021-22251?
CVE-2021-22251 affects GitLab versions from 12.2.0 to 13.12.9, 14.0.0 to 14.0.7, and 14.1.0 to 14.1.2.
Is there a workaround for CVE-2021-22251?
Currently, there is no official workaround for CVE-2021-22251; updating GitLab is recommended.