CVE-2018-18647: Medium severity gitlab vulnerability

Q: What is the severity of CVE-2018-18647?

CVE-2018-18647 has a critical severity due to the missing authorization vulnerabilities that can potentially allow unauthorized access to sensitive data.

Q: How do I fix CVE-2018-18647?

To fix CVE-2018-18647, upgrade GitLab to version 11.2.7, 11.3.8, or 11.4.3 or later.

Q: What are the affected versions in CVE-2018-18647?

CVE-2018-18647 affects GitLab Community and Enterprise Edition versions prior to 11.2.7, 11.3.x before 11.3.8, and 11.4.x before 11.4.3.

Q: What type of vulnerability is CVE-2018-18647?

CVE-2018-18647 is classified as a missing authorization vulnerability, which can lead to privilege escalation.

Q: Can CVE-2018-18647 lead to data breaches?

Yes, CVE-2018-18647 can potentially lead to data breaches by allowing unauthorized users to access sensitive information.

Published Dec 4, 2018

Updated

An issue was discovered in GitLab Community and Enterprise Edition before 11.2.7, 11.3.x before 11.3.8, and 11.4.x before 11.4.3. It has Missing Authorization.

Affected Software

6 affected components

GitLab GitLab>=8.11<11.2.7

GitLab GitLab>=11.3.0<11.3.8

GitLab GitLab>=11.4.0<11.4.3

Remediation

Patch Available

https://gitlab.com/gitlab-org/gitlab-ee/issues/7538

Event History

Dec 4, 2018

CVE Published

via MITRE·11:00 PM

Data Sourced

via MITRE·11:00 PM

Description

Frequently Asked Questions

What is the severity of CVE-2018-18647?

CVE-2018-18647 has a critical severity due to the missing authorization vulnerabilities that can potentially allow unauthorized access to sensitive data.

How do I fix CVE-2018-18647?