What is the severity of CVE-2018-20507?

The severity of CVE-2018-20507 is categorized as high due to incorrect access control allowing unauthorized access.

How do I fix CVE-2018-20507?

To fix CVE-2018-20507, upgrade GitLab to version 11.4.13 or higher for 11.4.x, 11.5.6 or higher for 11.5.x, or 11.6.1 or higher for 11.6.x.

What versions of GitLab are affected by CVE-2018-20507?

CVE-2018-20507 affects GitLab Enterprise and Community Editions from versions 11.2.x to 11.4.x before 11.4.13, 11.5.x before 11.5.6, and 11.6.x before 11.6.1.

What type of vulnerability is CVE-2018-20507?

CVE-2018-20507 is an incorrect access control vulnerability that can enable unauthorized access to certain resources.

Is there a workaround for CVE-2018-20507?

There are no specific workarounds for CVE-2018-20507; upgrading to a secure version is recommended.

Vulnerability/
CVE-2018-20507

medium

5.3

CWE

306

30/12/2019

5/8/2024

CVE-2018-20507

First published: Mon Dec 30 2019(Updated: )

An issue was discovered in GitLab Enterprise Edition 11.2.x through 11.4.x 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	>=11.2.0<11.4.13
GitLab	>=11.2.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

https://about.gitlab.com/2018/12/31/security-release-gitlab-11-dot-6-dot-1-released/

Frequently Asked Questions

What is the severity of CVE-2018-20507?
The severity of CVE-2018-20507 is categorized as high due to incorrect access control allowing unauthorized access.
How do I fix CVE-2018-20507?
To fix CVE-2018-20507, upgrade GitLab to version 11.4.13 or higher for 11.4.x, 11.5.6 or higher for 11.5.x, or 11.6.1 or higher for 11.6.x.
What versions of GitLab are affected by CVE-2018-20507?
CVE-2018-20507 affects GitLab Enterprise and Community Editions from versions 11.2.x to 11.4.x before 11.4.13, 11.5.x before 11.5.6, and 11.6.x before 11.6.1.
What type of vulnerability is CVE-2018-20507?
CVE-2018-20507 is an incorrect access control vulnerability that can enable unauthorized access to certain resources.
Is there a workaround for CVE-2018-20507?
There are no specific workarounds for CVE-2018-20507; upgrading to a secure version is recommended.

agent/type
agent/references
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/11.2.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-20507?
The severity of CVE-2018-20507 is categorized as high due to incorrect access control allowing unauthorized access.
How do I fix CVE-2018-20507?
To fix CVE-2018-20507, upgrade GitLab to version 11.4.13 or higher for 11.4.x, 11.5.6 or higher for 11.5.x, or 11.6.1 or higher for 11.6.x.
What versions of GitLab are affected by CVE-2018-20507?
CVE-2018-20507 affects GitLab Enterprise and Community Editions from versions 11.2.x to 11.4.x before 11.4.13, 11.5.x before 11.5.6, and 11.6.x before 11.6.1.
What type of vulnerability is CVE-2018-20507?
CVE-2018-20507 is an incorrect access control vulnerability that can enable unauthorized access to certain resources.
Is there a workaround for CVE-2018-20507?
There are no specific workarounds for CVE-2018-20507; upgrading to a secure version is recommended.