What is the severity of CVE-2020-13323?

CVE-2020-13323 has a moderate severity level as it affects the confidentiality of private merge requests.

How do I fix CVE-2020-13323?

To fix CVE-2020-13323, upgrade GitLab to the latest version that is not affected, specifically versions above 13.1.2.

Which GitLab versions are affected by CVE-2020-13323?

CVE-2020-13323 affects GitLab versions prior to 13.1 and several versions including 12.10.13 and 13.0.8.

What type of attack does CVE-2020-13323 represent?

CVE-2020-13323 represents a confidentiality attack where private merge requests can be unlawfully accessed.

How can I determine if my GitLab instance is vulnerable to CVE-2020-13323?

Check the version of your GitLab instance; if it is between 8.5.0 and 12.10.13 or between 13.0.0 and 13.1.2, it is vulnerable to CVE-2020-13323.

Vulnerability/
CVE-2020-13323

high

7.7

29/9/2020

4/8/2024

CVE-2020-13323

First published: Tue Sep 29 2020(Updated: )

A vulnerability was discovered in GitLab versions prior 13.1. Under certain conditions private merge requests could be read via Todos

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=8.5.0<12.10.13
GitLab	>=13.0.0<13.0.8
GitLab	>=13.1.0<13.1.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-13323?
CVE-2020-13323 has a moderate severity level as it affects the confidentiality of private merge requests.
How do I fix CVE-2020-13323?
To fix CVE-2020-13323, upgrade GitLab to the latest version that is not affected, specifically versions above 13.1.2.
Which GitLab versions are affected by CVE-2020-13323?
CVE-2020-13323 affects GitLab versions prior to 13.1 and several versions including 12.10.13 and 13.0.8.
What type of attack does CVE-2020-13323 represent?
CVE-2020-13323 represents a confidentiality attack where private merge requests can be unlawfully accessed.
How can I determine if my GitLab instance is vulnerable to CVE-2020-13323?
Check the version of your GitLab instance; if it is between 8.5.0 and 12.10.13 or between 13.0.0 and 13.1.2, it is vulnerable to CVE-2020-13323.

agent/references
agent/type
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/8.5.0
version/gitlab/13.0.0
version/gitlab/13.1.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-13323?
CVE-2020-13323 has a moderate severity level as it affects the confidentiality of private merge requests.
How do I fix CVE-2020-13323?
To fix CVE-2020-13323, upgrade GitLab to the latest version that is not affected, specifically versions above 13.1.2.
Which GitLab versions are affected by CVE-2020-13323?
CVE-2020-13323 affects GitLab versions prior to 13.1 and several versions including 12.10.13 and 13.0.8.
What type of attack does CVE-2020-13323 represent?
CVE-2020-13323 represents a confidentiality attack where private merge requests can be unlawfully accessed.
How can I determine if my GitLab instance is vulnerable to CVE-2020-13323?
Check the version of your GitLab instance; if it is between 8.5.0 and 12.10.13 or between 13.0.0 and 13.1.2, it is vulnerable to CVE-2020-13323.