CVE-2019-19629
First published: Sun Jan 05 2020(Updated: )
In GitLab EE 10.5 through 12.5.3, 12.4.5, and 12.3.8, when transferring a public project to a private group, private code would be disclosed via the Group Search API provided by the Elasticsearch integration.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=10.5.0<=12.3.8 | |
| GitLab | >=12.4.0<=12.4.5 | |
| GitLab | >=12.5.0<=12.5.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-19629?
CVE-2019-19629 is considered a medium severity vulnerability due to the potential exposure of private code.
How do I fix CVE-2019-19629?
To fix CVE-2019-19629, upgrade GitLab EE to version 12.5.4 or later.
What versions of GitLab are affected by CVE-2019-19629?
CVE-2019-19629 affects GitLab EE versions from 10.5 through 12.5.3 and certain versions of 12.4 and 12.3.
What type of information is exposed in CVE-2019-19629?
CVE-2019-19629 may lead to private code being disclosed when transferring a public project to a private group.
Is the Group Search API vulnerable due to CVE-2019-19629?
Yes, the Group Search API is accessible and may expose private code due to CVE-2019-19629.
- agent/references
- agent/type
- agent/severity
- agent/author
- 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/10.5.0
- version/gitlab/12.3.8
- version/gitlab/12.4.0
- version/gitlab/12.4.5
- version/gitlab/12.5.0
- version/gitlab/12.5.3