What is the severity of CVE-2020-13352?

CVE-2020-13352 is considered a medium severity vulnerability due to the potential exposure of sensitive group information.

How do I fix CVE-2020-13352?

To fix CVE-2020-13352, upgrade to GitLab versions 13.3.9, 13.4.5, or 13.5.2 or later, ensuring that private group settings are preserved during migration.

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

CVE-2020-13352 affects GitLab CE/EE versions from 10.2 to below 13.3.9, and also versions between 13.4 and below 13.4.5, as well as 13.5 to below 13.5.2.

What data is exposed in CVE-2020-13352?

CVE-2020-13352 results in the leakage of private group information when a project transitions from a private to a public group.

Is there a workaround for CVE-2020-13352?

The primary recommendation is to avoid changing project visibility settings from private to public in affected versions until an update can be applied.

Vulnerability/
CVE-2020-13352

medium

5.3

17/11/2020

4/8/2024

CVE-2020-13352

First published: Tue Nov 17 2020(Updated: )

Private group info is leaked leaked in GitLab CE/EE version 10.2 and above, when the project is moved from private to public group. Affected versions are: >=10.2, <13.3.9,>=13.4, <13.4.5,>=13.5, <13.5.2.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=10.2.0<13.3.9
GitLab	>=10.2.0<13.3.9
GitLab	>=13.4.0<13.4.5
GitLab	>=13.4.0<13.4.5
GitLab	>=13.5.0<13.5.2
GitLab	>=13.5.0<13.5.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-13352?
CVE-2020-13352 is considered a medium severity vulnerability due to the potential exposure of sensitive group information.
How do I fix CVE-2020-13352?
To fix CVE-2020-13352, upgrade to GitLab versions 13.3.9, 13.4.5, or 13.5.2 or later, ensuring that private group settings are preserved during migration.
Which GitLab versions are affected by CVE-2020-13352?
CVE-2020-13352 affects GitLab CE/EE versions from 10.2 to below 13.3.9, and also versions between 13.4 and below 13.4.5, as well as 13.5 to below 13.5.2.
What data is exposed in CVE-2020-13352?
CVE-2020-13352 results in the leakage of private group information when a project transitions from a private to a public group.
Is there a workaround for CVE-2020-13352?
The primary recommendation is to avoid changing project visibility settings from private to public in affected versions until an update can be applied.

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
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/10.2.0
version/gitlab/13.4.0
version/gitlab/13.5.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-13352?
CVE-2020-13352 is considered a medium severity vulnerability due to the potential exposure of sensitive group information.
How do I fix CVE-2020-13352?
To fix CVE-2020-13352, upgrade to GitLab versions 13.3.9, 13.4.5, or 13.5.2 or later, ensuring that private group settings are preserved during migration.
Which GitLab versions are affected by CVE-2020-13352?
CVE-2020-13352 affects GitLab CE/EE versions from 10.2 to below 13.3.9, and also versions between 13.4 and below 13.4.5, as well as 13.5 to below 13.5.2.
What data is exposed in CVE-2020-13352?
CVE-2020-13352 results in the leakage of private group information when a project transitions from a private to a public group.
Is there a workaround for CVE-2020-13352?
The primary recommendation is to avoid changing project visibility settings from private to public in affected versions until an update can be applied.