What is the severity of CVE-2020-6832?

CVE-2020-6832 has been classified as a medium-severity vulnerability.

How do I fix CVE-2020-6832?

To resolve CVE-2020-6832, upgrade your GitLab Enterprise Edition to version 12.6.2 or later.

What software versions are affected by CVE-2020-6832?

CVE-2020-6832 affects GitLab Enterprise Edition versions from 8.9.0 to 12.6.1 and GitLab Community Edition in the same version range.

What type of vulnerability is CVE-2020-6832?

CVE-2020-6832 is a data exposure vulnerability that allows unauthorized access to issues from private projects.

Is CVE-2020-6832 present in all GitLab installations?

CVE-2020-6832 is only present in GitLab installations running the vulnerable versions as specified in the affected software section.

Vulnerability/
CVE-2020-6832

medium

5.3

13/1/2020

4/8/2024

CVE-2020-6832

First published: Mon Jan 13 2020(Updated: )

An issue was discovered in GitLab Enterprise Edition (EE) 8.9.0 through 12.6.1. Using the project import feature, it was possible for someone to obtain issues from private projects.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=8.9.0<=12.6.1
GitLab	>=8.9.0<=12.6.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-6832?
CVE-2020-6832 has been classified as a medium-severity vulnerability.
How do I fix CVE-2020-6832?
To resolve CVE-2020-6832, upgrade your GitLab Enterprise Edition to version 12.6.2 or later.
What software versions are affected by CVE-2020-6832?
CVE-2020-6832 affects GitLab Enterprise Edition versions from 8.9.0 to 12.6.1 and GitLab Community Edition in the same version range.
What type of vulnerability is CVE-2020-6832?
CVE-2020-6832 is a data exposure vulnerability that allows unauthorized access to issues from private projects.
Is CVE-2020-6832 present in all GitLab installations?
CVE-2020-6832 is only present in GitLab installations running the vulnerable versions as specified in the affected software section.

agent/references
agent/type
agent/severity
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
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.9.0
version/gitlab/12.6.1

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-6832?
CVE-2020-6832 has been classified as a medium-severity vulnerability.
How do I fix CVE-2020-6832?
To resolve CVE-2020-6832, upgrade your GitLab Enterprise Edition to version 12.6.2 or later.
What software versions are affected by CVE-2020-6832?
CVE-2020-6832 affects GitLab Enterprise Edition versions from 8.9.0 to 12.6.1 and GitLab Community Edition in the same version range.
What type of vulnerability is CVE-2020-6832?
CVE-2020-6832 is a data exposure vulnerability that allows unauthorized access to issues from private projects.
Is CVE-2020-6832 present in all GitLab installations?
CVE-2020-6832 is only present in GitLab installations running the vulnerable versions as specified in the affected software section.