What is the severity of CVE-2020-5197?

CVE-2020-5197 is classified as a medium severity vulnerability due to its potential for unauthorized access to sensitive information.

How do I fix CVE-2020-5197?

To fix CVE-2020-5197, update GitLab Community Edition and Enterprise Edition to version 12.6.2 or later.

Which versions are affected by CVE-2020-5197?

CVE-2020-5197 affects GitLab versions from 5.1.0 to 12.6.1 inclusive.

What type of vulnerability is CVE-2020-5197?

CVE-2020-5197 is categorized as an Incorrect Access Control vulnerability.

What is the potential impact of CVE-2020-5197?

The potential impact of CVE-2020-5197 includes unauthorized access to confidential data or functionalities within GitLab.

Vulnerability/
CVE-2020-5197

medium

4.3

CWE

200

13/1/2020

4/8/2024

CVE-2020-5197: Infoleak

First published: Mon Jan 13 2020(Updated: )

An issue was discovered in GitLab Community Edition (CE) and Enterprise Edition (EE) 5.1 through 12.6.1. It has Incorrect Access Control.

Credit: cve@mitre.org

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-5197?
CVE-2020-5197 is classified as a medium severity vulnerability due to its potential for unauthorized access to sensitive information.
How do I fix CVE-2020-5197?
To fix CVE-2020-5197, update GitLab Community Edition and Enterprise Edition to version 12.6.2 or later.
Which versions are affected by CVE-2020-5197?
CVE-2020-5197 affects GitLab versions from 5.1.0 to 12.6.1 inclusive.
What type of vulnerability is CVE-2020-5197?
CVE-2020-5197 is categorized as an Incorrect Access Control vulnerability.
What is the potential impact of CVE-2020-5197?
The potential impact of CVE-2020-5197 includes unauthorized access to confidential data or functionalities within GitLab.

agent/references
agent/type
agent/severity
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/5.1.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-5197?
CVE-2020-5197 is classified as a medium severity vulnerability due to its potential for unauthorized access to sensitive information.
How do I fix CVE-2020-5197?
To fix CVE-2020-5197, update GitLab Community Edition and Enterprise Edition to version 12.6.2 or later.
Which versions are affected by CVE-2020-5197?
CVE-2020-5197 affects GitLab versions from 5.1.0 to 12.6.1 inclusive.
What type of vulnerability is CVE-2020-5197?
CVE-2020-5197 is categorized as an Incorrect Access Control vulnerability.
What is the potential impact of CVE-2020-5197?
The potential impact of CVE-2020-5197 includes unauthorized access to confidential data or functionalities within GitLab.