What is the severity of CVE-2020-13313?

CVE-2020-13313 has a medium severity rating due to the unauthorized modification of subgroup badges.

How do I fix CVE-2020-13313?

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

What versions of GitLab are affected by CVE-2020-13313?

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

Who can exploit CVE-2020-13313?

An unauthorized project maintainer can exploit CVE-2020-13313 to modify subgroup badges.

Is CVE-2020-13313 a critical vulnerability?

CVE-2020-13313 is not classified as critical, but it can lead to unauthorized changes in project settings.

Vulnerability/
CVE-2020-13313

medium

4.3

CWE

863

14/9/2020

4/8/2024

CVE-2020-13313

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 unauthorized project maintainer could edit the subgroup badges due to the lack of authorization control.

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-13313?
CVE-2020-13313 has a medium severity rating due to the unauthorized modification of subgroup badges.
How do I fix CVE-2020-13313?
To fix CVE-2020-13313, upgrade GitLab to version 13.1.10 or later, 13.2.8 or later, or 13.3.4 or later.
What versions of GitLab are affected by CVE-2020-13313?
CVE-2020-13313 affects GitLab versions prior to 13.1.10, 13.2.8, and 13.3.4.
Who can exploit CVE-2020-13313?
An unauthorized project maintainer can exploit CVE-2020-13313 to modify subgroup badges.
Is CVE-2020-13313 a critical vulnerability?
CVE-2020-13313 is not classified as critical, but it can lead to unauthorized changes in project settings.

agent/type
agent/references
agent/author
agent/weakness
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-13313?
CVE-2020-13313 has a medium severity rating due to the unauthorized modification of subgroup badges.
How do I fix CVE-2020-13313?
To fix CVE-2020-13313, upgrade GitLab to version 13.1.10 or later, 13.2.8 or later, or 13.3.4 or later.
What versions of GitLab are affected by CVE-2020-13313?
CVE-2020-13313 affects GitLab versions prior to 13.1.10, 13.2.8, and 13.3.4.
Who can exploit CVE-2020-13313?
An unauthorized project maintainer can exploit CVE-2020-13313 to modify subgroup badges.
Is CVE-2020-13313 a critical vulnerability?
CVE-2020-13313 is not classified as critical, but it can lead to unauthorized changes in project settings.