CVE-2019-19628: Path Traversal
First published: Sun Jan 05 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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=11.3.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-19628?
CVE-2019-19628 has a high severity level due to its potential for privilege escalation and remote code execution.
How do I fix CVE-2019-19628?
To fix CVE-2019-19628, update GitLab to a version later than 12.5.4.
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.
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.
Which GitLab product is vulnerable in CVE-2019-19628?
CVE-2019-19628 specifically affects the GitLab Enterprise Editions.
- agent/references
- agent/type
- agent/weakness
- agent/author
- 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.3.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