What is the severity of CVE-2018-20493?

CVE-2018-20493 has a high severity due to the incorrect access control vulnerability which may lead to unauthorized access.

How do I fix CVE-2018-20493?

To fix CVE-2018-20493, upgrade your GitLab installation to version 11.4.13, 11.5.6, or 11.6.1 or later.

Which GitLab versions are affected by CVE-2018-20493?

CVE-2018-20493 affects GitLab Community and Enterprise Editions before versions 11.4.13, 11.5.6, and 11.6.1.

What type of vulnerability is CVE-2018-20493?

CVE-2018-20493 is classified as an access control vulnerability.

Can CVE-2018-20493 impact my data security?

Yes, CVE-2018-20493 can significantly impact data security by allowing unauthorized users to access sensitive information.

Vulnerability/
CVE-2018-20493

medium

4.3

CWE

863

30/12/2019

5/8/2024

CVE-2018-20493

First published: Mon Dec 30 2019(Updated: )

An issue was discovered in GitLab Community and Enterprise Edition before 11.4.13, 11.5.x before 11.5.6, and 11.6.x before 11.6.1. It has Incorrect Access Control.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=8.17.0<11.4.13
GitLab	>=8.17.0<11.4.13
GitLab	>=11.5.0<11.5.6
GitLab	>=11.5.0<11.5.6
GitLab	>=11.6.0<11.6.1
GitLab	>=11.6.0<11.6.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-20493?
CVE-2018-20493 has a high severity due to the incorrect access control vulnerability which may lead to unauthorized access.
How do I fix CVE-2018-20493?
To fix CVE-2018-20493, upgrade your GitLab installation to version 11.4.13, 11.5.6, or 11.6.1 or later.
Which GitLab versions are affected by CVE-2018-20493?
CVE-2018-20493 affects GitLab Community and Enterprise Editions before versions 11.4.13, 11.5.6, and 11.6.1.
What type of vulnerability is CVE-2018-20493?
CVE-2018-20493 is classified as an access control vulnerability.
Can CVE-2018-20493 impact my data security?
Yes, CVE-2018-20493 can significantly impact data security by allowing unauthorized users to access sensitive information.

agent/references
agent/type
agent/severity
agent/weakness
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.17.0
version/gitlab/11.5.0
version/gitlab/11.6.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-2018-20493?
CVE-2018-20493 has a high severity due to the incorrect access control vulnerability which may lead to unauthorized access.
How do I fix CVE-2018-20493?
To fix CVE-2018-20493, upgrade your GitLab installation to version 11.4.13, 11.5.6, or 11.6.1 or later.
Which GitLab versions are affected by CVE-2018-20493?
CVE-2018-20493 affects GitLab Community and Enterprise Editions before versions 11.4.13, 11.5.6, and 11.6.1.
What type of vulnerability is CVE-2018-20493?
CVE-2018-20493 is classified as an access control vulnerability.
Can CVE-2018-20493 impact my data security?
Yes, CVE-2018-20493 can significantly impact data security by allowing unauthorized users to access sensitive information.