CVE-2019-18460: Infoleak
First published: Tue Nov 26 2019(Updated: )
An issue was discovered in GitLab Community and Enterprise Edition 8.15 through 12.4 in the Comments Search feature provided by the Elasticsearch integration. It has Incorrect Access Control.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=8.15.0<=12.4.0 | |
| GitLab | >=8.15.0<=12.4.0 |
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-2019-18460?
CVE-2019-18460 has been classified as a high-severity vulnerability due to incorrect access control in GitLab.
How do I fix CVE-2019-18460?
To fix CVE-2019-18460, upgrade GitLab to version 12.4.1 or later.
What versions of GitLab are affected by CVE-2019-18460?
CVE-2019-18460 affects GitLab Community and Enterprise Editions from version 8.15 to 12.4.
What type of vulnerability is CVE-2019-18460?
CVE-2019-18460 is an access control vulnerability impacting the Comments Search feature in GitLab.
Does CVE-2019-18460 affect all users of GitLab?
CVE-2019-18460 primarily affects GitLab users who utilize the Elasticsearch integration for Comments Search.
- agent/references
- agent/type
- agent/weakness
- agent/author
- agent/severity
- 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/8.15.0
- version/gitlab/12.4.0