CVE-2018-20499: SSRF
Published Dec 30, 2019
·Updated
An issue was discovered in GitLab Community and Enterprise Edition before 11.x before 11.4.13, 11.5.x before 11.5.6, and 11.6.x before 11.6.1. It allows SSRF.
Affected Software
6 affected components
GitLab GitLab>=11.0.0<11.4.13
GitLab GitLab>=11.0.0<11.4.13
GitLab GitLab>=11.5.0<11.5.6
GitLab GitLab>=11.5.0<11.5.6
GitLab GitLab>=11.6.0<11.6.1
GitLab GitLab>=11.6.0<11.6.1
Event History
Dec 30, 2019
CVE Published
via MITRE·09:24 PM
Data Sourced
via MITRE·09:24 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2018-20499?
CVE-2018-20499 has a medium severity rating due to its potential to enable server-side request forgery (SSRF) attacks.
2
How do I fix CVE-2018-20499?
To fix CVE-2018-20499, upgrade GitLab to versions 11.4.13, 11.5.6, or 11.6.1 or later.
3
What versions of GitLab are affected by CVE-2018-20499?
CVE-2018-20499 affects GitLab Community and Enterprise Editions before versions 11.4.13, 11.5.6, and 11.6.1.
4
What type of vulnerability is CVE-2018-20499?
CVE-2018-20499 is classified as a server-side request forgery (SSRF) vulnerability.
5
Is CVE-2018-20499 present in older GitLab versions?
Yes, CVE-2018-20499 is present in GitLab versions prior to 11.4.13, 11.5.6, and 11.6.1.