What is the severity of CVE-2020-13317?

CVE-2020-13317 is considered a high severity vulnerability due to its potential impact on repository deletion by maintainers.

How do I fix CVE-2020-13317?

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

What types of GitLab versions are affected by CVE-2020-13317?

CVE-2020-13317 affects GitLab Community and Enterprise editions prior to versions 13.1.10, 13.2.8, and 13.3.4.

What is the impact of CVE-2020-13317?

The impact of CVE-2020-13317 allows unauthorized deletion of repositories by maintainers due to insufficient checks in the GraphQL API.

Is CVE-2020-13317 related to GraphQL vulnerabilities?

Yes, CVE-2020-13317 involves a vulnerability in the GraphQL API that permits inappropriate repository deletion.

Vulnerability/
CVE-2020-13317

medium

6.5

CWE

14/9/2020

4/8/2024

CVE-2020-13317: Input Validation

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. An insufficient check in the GraphQL api allowed a maintainer to delete a repository.

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-13317?
CVE-2020-13317 is considered a high severity vulnerability due to its potential impact on repository deletion by maintainers.
How do I fix CVE-2020-13317?
To fix CVE-2020-13317, upgrade GitLab to versions 13.1.10, 13.2.8, or 13.3.4 or later.
What types of GitLab versions are affected by CVE-2020-13317?
CVE-2020-13317 affects GitLab Community and Enterprise editions prior to versions 13.1.10, 13.2.8, and 13.3.4.
What is the impact of CVE-2020-13317?
The impact of CVE-2020-13317 allows unauthorized deletion of repositories by maintainers due to insufficient checks in the GraphQL API.
Is CVE-2020-13317 related to GraphQL vulnerabilities?
Yes, CVE-2020-13317 involves a vulnerability in the GraphQL API that permits inappropriate repository deletion.

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.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-13317?
CVE-2020-13317 is considered a high severity vulnerability due to its potential impact on repository deletion by maintainers.
How do I fix CVE-2020-13317?
To fix CVE-2020-13317, upgrade GitLab to versions 13.1.10, 13.2.8, or 13.3.4 or later.
What types of GitLab versions are affected by CVE-2020-13317?
CVE-2020-13317 affects GitLab Community and Enterprise editions prior to versions 13.1.10, 13.2.8, and 13.3.4.
What is the impact of CVE-2020-13317?
The impact of CVE-2020-13317 allows unauthorized deletion of repositories by maintainers due to insufficient checks in the GraphQL API.
Is CVE-2020-13317 related to GraphQL vulnerabilities?
Yes, CVE-2020-13317 involves a vulnerability in the GraphQL API that permits inappropriate repository deletion.