What is the severity of CVE-2021-22243?

CVE-2021-22243 is classified as a medium severity vulnerability that can allow unauthorized access to groups.

How do I fix CVE-2021-22243?

To mitigate CVE-2021-22243, upgrade GitLab to the latest version that contains the security fix.

Which GitLab versions are affected by CVE-2021-22243?

GitLab CE/EE versions from 7.10 to 14.1.2 are affected by CVE-2021-22243.

What impact does CVE-2021-22243 have on GitLab users?

CVE-2021-22243 allows existing GitLab users to access groups using invite URLs meant for different email addresses.

Is there a known exploit for CVE-2021-22243?

There are no publicly reported exploits specifically targeting CVE-2021-22243, but it poses a security risk if left unpatched.

Vulnerability/
CVE-2021-22243

medium

CWE

863

25/8/2021

3/8/2024

CVE-2021-22243

First published: Wed Aug 25 2021(Updated: )

Under specialized conditions, GitLab CE/EE versions starting 7.10 may allow existing GitLab users to use an invite URL meant for another email address to gain access into a group.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=7.10.0<13.12.9
GitLab	>=7.10.0<13.12.9
GitLab	>=14.0.0<14.0.7
GitLab	>=14.0.0<14.0.7
GitLab	>=14.1.0<14.1.2
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-22243?
CVE-2021-22243 is classified as a medium severity vulnerability that can allow unauthorized access to groups.
How do I fix CVE-2021-22243?
To mitigate CVE-2021-22243, upgrade GitLab to the latest version that contains the security fix.
Which GitLab versions are affected by CVE-2021-22243?
GitLab CE/EE versions from 7.10 to 14.1.2 are affected by CVE-2021-22243.
What impact does CVE-2021-22243 have on GitLab users?
CVE-2021-22243 allows existing GitLab users to access groups using invite URLs meant for different email addresses.
Is there a known exploit for CVE-2021-22243?
There are no publicly reported exploits specifically targeting CVE-2021-22243, but it poses a security risk if left unpatched.

agent/references
agent/type
agent/weakness
agent/author
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/7.10.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-22243?
CVE-2021-22243 is classified as a medium severity vulnerability that can allow unauthorized access to groups.
How do I fix CVE-2021-22243?
To mitigate CVE-2021-22243, upgrade GitLab to the latest version that contains the security fix.
Which GitLab versions are affected by CVE-2021-22243?
GitLab CE/EE versions from 7.10 to 14.1.2 are affected by CVE-2021-22243.
What impact does CVE-2021-22243 have on GitLab users?
CVE-2021-22243 allows existing GitLab users to access groups using invite URLs meant for different email addresses.
Is there a known exploit for CVE-2021-22243?
There are no publicly reported exploits specifically targeting CVE-2021-22243, but it poses a security risk if left unpatched.