CVE-2018-20498
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.10.0<11.4.13 | |
| GitLab | >=8.10.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
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-20498?
CVE-2018-20498 is classified as a high severity vulnerability due to incorrect access control allowing unauthorized actions.
How do I fix CVE-2018-20498?
To fix CVE-2018-20498, upgrade your GitLab installation to version 11.4.13, 11.5.6, or 11.6.1 or later.
What versions of GitLab are affected by CVE-2018-20498?
CVE-2018-20498 affects GitLab Community and Enterprise Editions before versions 11.4.13, 11.5.6, and 11.6.1.
What type of issue is CVE-2018-20498?
CVE-2018-20498 pertains to an issue of incorrect access control in GitLab.
Is there a risk of data exposure with CVE-2018-20498?
Yes, CVE-2018-20498 poses a risk of potential data exposure due to unauthorized access to restricted functionalities.
- agent/references
- agent/type
- agent/author
- agent/weakness
- agent/severity
- 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.10.0
- version/gitlab/11.5.0
- version/gitlab/11.6.0