What is the severity of CVE-2020-10535?

CVE-2020-10535 has a medium severity rating due to its potential to allow unauthorized access during a specific grace period.

How do I fix CVE-2020-10535?

To fix CVE-2020-10535, upgrade GitLab to version 12.8.6 or later immediately to close the vulnerability.

What platforms are affected by CVE-2020-10535?

CVE-2020-10535 affects GitLab versions 12.8.0 to 12.8.5 for both Community and Enterprise editions.

What is the impact of CVE-2020-10535 on my GitLab instance?

The impact of CVE-2020-10535 allows attackers to bypass email domain restrictions if sign-up is enabled.

Is there a workaround for CVE-2020-10535 while I update my system?

There is no official workaround for CVE-2020-10535, so upgrading to the patched version is recommended.

Vulnerability/
CVE-2020-10535

medium

5.3

12/3/2020

4/8/2024

CVE-2020-10535

First published: Thu Mar 12 2020(Updated: )

GitLab 12.8.x before 12.8.6, when sign-up is enabled, allows remote attackers to bypass email domain restrictions within the two-day grace period for an unconfirmed email address.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=12.8.0<12.8.6
GitLab	>=12.8.0<12.8.6

Never miss a vulnerability like this again

Reference Links

https://about.gitlab.com/releases/2020/03/11/critical-security-release-gitlab-12-dot-8-dot-6-released/

Frequently Asked Questions

What is the severity of CVE-2020-10535?
CVE-2020-10535 has a medium severity rating due to its potential to allow unauthorized access during a specific grace period.
How do I fix CVE-2020-10535?
To fix CVE-2020-10535, upgrade GitLab to version 12.8.6 or later immediately to close the vulnerability.
What platforms are affected by CVE-2020-10535?
CVE-2020-10535 affects GitLab versions 12.8.0 to 12.8.5 for both Community and Enterprise editions.
What is the impact of CVE-2020-10535 on my GitLab instance?
The impact of CVE-2020-10535 allows attackers to bypass email domain restrictions if sign-up is enabled.
Is there a workaround for CVE-2020-10535 while I update my system?
There is no official workaround for CVE-2020-10535, so upgrading to the patched version is recommended.

agent/type
agent/references
agent/severity
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
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.8.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-10535?
CVE-2020-10535 has a medium severity rating due to its potential to allow unauthorized access during a specific grace period.
How do I fix CVE-2020-10535?
To fix CVE-2020-10535, upgrade GitLab to version 12.8.6 or later immediately to close the vulnerability.
What platforms are affected by CVE-2020-10535?
CVE-2020-10535 affects GitLab versions 12.8.0 to 12.8.5 for both Community and Enterprise editions.
What is the impact of CVE-2020-10535 on my GitLab instance?
The impact of CVE-2020-10535 allows attackers to bypass email domain restrictions if sign-up is enabled.
Is there a workaround for CVE-2020-10535 while I update my system?
There is no official workaround for CVE-2020-10535, so upgrading to the patched version is recommended.