What is the severity of CVE-2020-13275?

CVE-2020-13275 has a severity rating of Medium, indicating a moderate level of risk.

How do I fix CVE-2020-13275?

To mitigate CVE-2020-13275, users should upgrade to GitLab version 12.9.9 or later for 12.x or 13.0.1 or later for 13.x.

What is the impact of CVE-2020-13275?

CVE-2020-13275 allows a user with an unverified email address to request access to domain-restricted groups.

Which versions of GitLab are affected by CVE-2020-13275?

CVE-2020-13275 affects GitLab versions from 12.2.0 through 13.0.0 but is addressed in later versions.

Is there a workaround for CVE-2020-13275 before upgrading?

No specific workaround is provided for CVE-2020-13275, so upgrading is the recommended action.

Vulnerability/
CVE-2020-13275

high

8.1

19/6/2020

4/8/2024

CVE-2020-13275

First published: Fri Jun 19 2020(Updated: )

A user with an unverified email address could request an access to domain restricted groups in GitLab EE 12.2 and later through 13.0.1

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.2.0<12.9.8
GitLab	>=12.2.0<12.9.8
GitLab	>=12.10.0<12.10.7
GitLab	>=12.10.0<12.10.7
GitLab	=13.0.0
GitLab	=13.0.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-13275?
CVE-2020-13275 has a severity rating of Medium, indicating a moderate level of risk.
How do I fix CVE-2020-13275?
To mitigate CVE-2020-13275, users should upgrade to GitLab version 12.9.9 or later for 12.x or 13.0.1 or later for 13.x.
What is the impact of CVE-2020-13275?
CVE-2020-13275 allows a user with an unverified email address to request access to domain-restricted groups.
Which versions of GitLab are affected by CVE-2020-13275?
CVE-2020-13275 affects GitLab versions from 12.2.0 through 13.0.0 but is addressed in later versions.
Is there a workaround for CVE-2020-13275 before upgrading?
No specific workaround is provided for CVE-2020-13275, so upgrading is the recommended action.

agent/type
agent/references
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/12.2.0
version/gitlab/12.10.0
version/gitlab/13.0.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-2020-13275?
CVE-2020-13275 has a severity rating of Medium, indicating a moderate level of risk.
How do I fix CVE-2020-13275?
To mitigate CVE-2020-13275, users should upgrade to GitLab version 12.9.9 or later for 12.x or 13.0.1 or later for 13.x.
What is the impact of CVE-2020-13275?
CVE-2020-13275 allows a user with an unverified email address to request access to domain-restricted groups.
Which versions of GitLab are affected by CVE-2020-13275?
CVE-2020-13275 affects GitLab versions from 12.2.0 through 13.0.0 but is addressed in later versions.
Is there a workaround for CVE-2020-13275 before upgrading?
No specific workaround is provided for CVE-2020-13275, so upgrading is the recommended action.