CVE-2019-19629

Description

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.

7.5

CVSS

Severity: High

CVSS 3.1 •

CVSS 2.0 •

EPSS 0.09%

Vendor Advisory gitlab.com

Affected: n/a n/a

References

Link	Tags
https://about.gitlab.com/blog/categories/releases/	release notes
https://about.gitlab.com/blog/2019/12/10/critical-security-release-gitlab-12-5-4-released/	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2019-19629?: CVE-2019-19629 has been scored as a high severity vulnerability.
How to fix CVE-2019-19629?: To fix CVE-2019-19629, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2019-19629 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2019-19629 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.