What is the severity of CVE-2020-13265?

CVE-2020-13265 is classified as a high severity vulnerability due to the potential for unauthorized access.

How do I fix CVE-2020-13265?

To fix CVE-2020-13265, upgrade GitLab to the latest version that has addressed this vulnerability.

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

CVE-2020-13265 affects GitLab versions from 12.5.0 to 12.9.8 and 12.10.0 to 12.10.7, including version 13.0.0.

What impact does CVE-2020-13265 have on user accounts?

CVE-2020-13265 allows users to bypass email verification, potentially leading to unauthorized account access.

Is CVE-2020-13265 present in both GitLab CE and EE?

Yes, CVE-2020-13265 is present in both GitLab Community Edition (CE) and GitLab Enterprise Edition (EE) versions.

Vulnerability/
CVE-2020-13265

medium

5.3

CWE

345

19/6/2020

4/8/2024

CVE-2020-13265

First published: Fri Jun 19 2020(Updated: )

User email verification bypass in GitLab CE/EE 12.5 and later through 13.0.1 allows user to bypass email verification

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.5.0<12.9.8
GitLab	>=12.5.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-13265?
CVE-2020-13265 is classified as a high severity vulnerability due to the potential for unauthorized access.
How do I fix CVE-2020-13265?
To fix CVE-2020-13265, upgrade GitLab to the latest version that has addressed this vulnerability.
Which versions of GitLab are affected by CVE-2020-13265?
CVE-2020-13265 affects GitLab versions from 12.5.0 to 12.9.8 and 12.10.0 to 12.10.7, including version 13.0.0.
What impact does CVE-2020-13265 have on user accounts?
CVE-2020-13265 allows users to bypass email verification, potentially leading to unauthorized account access.
Is CVE-2020-13265 present in both GitLab CE and EE?
Yes, CVE-2020-13265 is present in both GitLab Community Edition (CE) and GitLab Enterprise Edition (EE) versions.

agent/type
agent/references
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/12.5.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-13265?
CVE-2020-13265 is classified as a high severity vulnerability due to the potential for unauthorized access.
How do I fix CVE-2020-13265?
To fix CVE-2020-13265, upgrade GitLab to the latest version that has addressed this vulnerability.
Which versions of GitLab are affected by CVE-2020-13265?
CVE-2020-13265 affects GitLab versions from 12.5.0 to 12.9.8 and 12.10.0 to 12.10.7, including version 13.0.0.
What impact does CVE-2020-13265 have on user accounts?
CVE-2020-13265 allows users to bypass email verification, potentially leading to unauthorized account access.
Is CVE-2020-13265 present in both GitLab CE and EE?
Yes, CVE-2020-13265 is present in both GitLab Community Edition (CE) and GitLab Enterprise Edition (EE) versions.