What is the severity of CVE-2020-13316?

CVE-2020-13316 has a medium severity rating due to its potential to allow unauthorized access to disabled repositories.

How do I fix CVE-2020-13316?

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

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

CVE-2020-13316 affects GitLab versions prior to 13.1.10, 13.2.8, and 13.3.4.

What kind of vulnerability is CVE-2020-13316?

CVE-2020-13316 is a security vulnerability related to improper validation of Deploy-Tokens.

Can I still access my repositories if I have CVE-2020-13316?

Yes, if you are using an affected version, your disabled repositories may still be accessible via the git command line.

Vulnerability/
CVE-2020-13316

medium

5.4

14/9/2020

4/8/2024

CVE-2020-13316

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. GitLab was not validating a Deploy-Token and allowed a disabled repository be accessible via a git command line.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.1.0<13.1.10
GitLab	>=13.1.0<13.1.10
GitLab	>=13.2.0<13.2.8
GitLab	>=13.2.0<13.2.8
GitLab	>=13.3.0<13.3.4
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-13316?
CVE-2020-13316 has a medium severity rating due to its potential to allow unauthorized access to disabled repositories.
How do I fix CVE-2020-13316?
To fix CVE-2020-13316, upgrade your GitLab installation to version 13.1.10, 13.2.8, or 13.3.4 or later.
Which versions of GitLab are affected by CVE-2020-13316?
CVE-2020-13316 affects GitLab versions prior to 13.1.10, 13.2.8, and 13.3.4.
What kind of vulnerability is CVE-2020-13316?
CVE-2020-13316 is a security vulnerability related to improper validation of Deploy-Tokens.
Can I still access my repositories if I have CVE-2020-13316?
Yes, if you are using an affected version, your disabled repositories may still be accessible via the git command line.

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/13.1.0
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-13316?
CVE-2020-13316 has a medium severity rating due to its potential to allow unauthorized access to disabled repositories.
How do I fix CVE-2020-13316?
To fix CVE-2020-13316, upgrade your GitLab installation to version 13.1.10, 13.2.8, or 13.3.4 or later.
Which versions of GitLab are affected by CVE-2020-13316?
CVE-2020-13316 affects GitLab versions prior to 13.1.10, 13.2.8, and 13.3.4.
What kind of vulnerability is CVE-2020-13316?
CVE-2020-13316 is a security vulnerability related to improper validation of Deploy-Tokens.
Can I still access my repositories if I have CVE-2020-13316?
Yes, if you are using an affected version, your disabled repositories may still be accessible via the git command line.