CVE-2019-19628: Path Traversal
Published Jan 5, 2020
·Updated
In GitLab EE 11.3 through 12.5.3, 12.4.5, and 12.3.8, insufficient parameter sanitization for the Maven package registry could lead to privilege escalation and remote code execution vulnerabilities under certain conditions.
Affected Software
3 affected components
GitLab GitLab>=11.3.0<=12.3.8
GitLab GitLab>=12.4.0<=12.4.5
GitLab GitLab>=12.5.0<=12.5.3
Event History
Jan 5, 2020
CVE Published
via MITRE·09:51 PM
Data Sourced
via MITRE·09:51 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2019-19628?
CVE-2019-19628 has a high severity level due to its potential for privilege escalation and remote code execution.
2
How do I fix CVE-2019-19628?
To fix CVE-2019-19628, update GitLab to a version later than 12.5.4.
3
What software versions are affected by CVE-2019-19628?
CVE-2019-19628 affects GitLab EE versions from 11.3.0 up to 12.5.3, 12.4.5, and 12.3.8.
4
What vulnerabilities are associated with insufficient parameter sanitization in CVE-2019-19628?
Insufficient parameter sanitization in CVE-2019-19628 can lead to privilege escalation and remote code execution vulnerabilities.
5
Which GitLab product is vulnerable in CVE-2019-19628?
CVE-2019-19628 specifically affects the GitLab Enterprise Editions.