What is the severity of CVE-2020-13302?

CVE-2020-13302 has a medium severity level as it can lead to unauthorized access to user accounts.

How do I fix CVE-2020-13302?

To fix CVE-2020-13302, upgrade your GitLab installation to versions 13.1.10, 13.2.8, or 13.3.4 or later.

What are the affected versions of GitLab for CVE-2020-13302?

The affected versions for CVE-2020-13302 are all GitLab versions prior to 13.1.10, 13.2.8, and 13.3.4.

What causes CVE-2020-13302 in GitLab?

CVE-2020-13302 is caused by GitLab failing to properly revoke user sessions, allowing access with old passwords under specific conditions.

Is my GitLab instance vulnerable to CVE-2020-13302?

If you are running GitLab versions earlier than 13.1.10, 13.2.8, or 13.3.4, then your instance is vulnerable to CVE-2020-13302.

Vulnerability/
CVE-2020-13302

high

7.2

CWE

613

14/9/2020

4/8/2024

CVE-2020-13302

First published: Mon Sep 14 2020(Updated: )

A vulnerability was discovered in GitLab versions before 13.1.10, 13.2.8 and 13.3.4. Under certain conditions GitLab was not properly revoking user sessions and allowed a malicious user to access a user account with an old password.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<13.1.10
GitLab	>=13.2.0<13.2.8
GitLab	>=13.3.0<13.3.4

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-13302?
CVE-2020-13302 has a medium severity level as it can lead to unauthorized access to user accounts.
How do I fix CVE-2020-13302?
To fix CVE-2020-13302, upgrade your GitLab installation to versions 13.1.10, 13.2.8, or 13.3.4 or later.
What are the affected versions of GitLab for CVE-2020-13302?
The affected versions for CVE-2020-13302 are all GitLab versions prior to 13.1.10, 13.2.8, and 13.3.4.
What causes CVE-2020-13302 in GitLab?
CVE-2020-13302 is caused by GitLab failing to properly revoke user sessions, allowing access with old passwords under specific conditions.
Is my GitLab instance vulnerable to CVE-2020-13302?
If you are running GitLab versions earlier than 13.1.10, 13.2.8, or 13.3.4, then your instance is vulnerable to CVE-2020-13302.

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/13.2.0
version/gitlab/13.3.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-13302?
CVE-2020-13302 has a medium severity level as it can lead to unauthorized access to user accounts.
How do I fix CVE-2020-13302?
To fix CVE-2020-13302, upgrade your GitLab installation to versions 13.1.10, 13.2.8, or 13.3.4 or later.
What are the affected versions of GitLab for CVE-2020-13302?
The affected versions for CVE-2020-13302 are all GitLab versions prior to 13.1.10, 13.2.8, and 13.3.4.
What causes CVE-2020-13302 in GitLab?
CVE-2020-13302 is caused by GitLab failing to properly revoke user sessions, allowing access with old passwords under specific conditions.
Is my GitLab instance vulnerable to CVE-2020-13302?
If you are running GitLab versions earlier than 13.1.10, 13.2.8, or 13.3.4, then your instance is vulnerable to CVE-2020-13302.