CVE-2019-5487
First published: Wed Dec 18 2019(Updated: )
An improper access control vulnerability exists in Gitlab EE <v12.3.3, <v12.2.7, & <v12.1.13 that allowed the group search feature with Elasticsearch to return private code, merge requests and commits.
Credit: support@hackerone.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | <12.1.13 | |
| GitLab | >=12.2.0<12.2.7 | |
| GitLab | >=12.3.0<12.3.3 |
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-5487?
CVE-2019-5487 is considered a high severity vulnerability due to its impact on private data exposure.
How do I fix CVE-2019-5487?
To fix CVE-2019-5487, upgrade GitLab EE to version 12.3.3 or later, or to version 12.2.7 or later, or to version 12.1.13 or later.
What kind of data can be exposed due to CVE-2019-5487?
CVE-2019-5487 can expose private code, merge requests, and commits through the group search feature with Elasticsearch.
Which versions of GitLab are affected by CVE-2019-5487?
CVE-2019-5487 affects GitLab EE versions prior to 12.1.13, 12.2.7, and 12.3.3.
Is CVE-2019-5487 specific to GitLab EE?
Yes, CVE-2019-5487 specifically affects GitLab Enterprise Edition.
- agent/type
- agent/references
- agent/weakness
- agent/author
- 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/12.2.0
- version/gitlab/12.3.0