CVE-2018-17939: Infoleak
First published: Tue Dec 04 2018(Updated: )
An issue was discovered in GitLab Community and Enterprise Edition 11.1.x before 11.1.8, 11.2.x before 11.2.5, and 11.3.x before 11.3.2. There is Information Exposure via the merge request JSON endpoint.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=11.1.0<11.1.8 | |
| GitLab | >=11.1.0<11.1.8 | |
| GitLab | >=11.2.0<11.2.5 | |
| GitLab | >=11.2.0<11.2.5 | |
| GitLab | >=11.3.0<11.3.2 | |
| GitLab | >=11.3.0<11.3.2 |
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-17939?
CVE-2018-17939 has a medium severity rating due to the potential for information exposure.
How do I fix CVE-2018-17939?
To fix CVE-2018-17939, upgrade GitLab to version 11.1.8, 11.2.5, or 11.3.2 or later.
What types of GitLab editions are affected by CVE-2018-17939?
Both GitLab Community and Enterprise Editions are affected by CVE-2018-17939.
Which versions of GitLab are vulnerable to CVE-2018-17939?
GitLab versions 11.1.x before 11.1.8, 11.2.x before 11.2.5, and 11.3.x before 11.3.2 are vulnerable to CVE-2018-17939.
What kind of information is exposed by CVE-2018-17939?
CVE-2018-17939 allows for information exposure via the merge request JSON endpoint.
- agent/references
- agent/type
- agent/author
- agent/weakness
- 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/11.1.0
- version/gitlab/11.2.0
- version/gitlab/11.3.0