CVE-2019-9890: Critical severity gitlab vulnerability
Published Apr 17, 2019
·Updated
An issue was discovered in GitLab Community and Enterprise Edition 10.x and 11.x before 11.6.10, 11.7.x before 11.7.6, and 11.8.x before 11.8.1. It has Insecure Permissions.
Affected Software
6 affected components
GitLab GitLab>=10.0.0<11.6.10
GitLab GitLab>=10.0.0<11.6.10
GitLab GitLab>=11.7.0<11.7.6
GitLab GitLab>=11.7.0<11.7.6
GitLab GitLab>=11.8.0<11.8.1
GitLab GitLab>=11.8.0<11.8.1
Event History
Apr 17, 2019
CVE Published
via MITRE·04:34 PM
Data Sourced
via MITRE·04:34 PM
Description
Data Sourced
via NVD·05:29 PM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2019-9890?
CVE-2019-9890 has been classified as a medium severity vulnerability due to its impact on secure permissions.
2
How do I fix CVE-2019-9890?
To resolve CVE-2019-9890, you should upgrade your GitLab installation to version 11.6.10, 11.7.6, or 11.8.1 or later.
3
Which versions of GitLab are affected by CVE-2019-9890?
CVE-2019-9890 affects GitLab Community and Enterprise Editions from version 10.x to prior to version 11.6.10, and specific vulnerable versions in the 11.x branch.
4
What type of vulnerability is CVE-2019-9890?
CVE-2019-9890 is categorized as an Insecure Permissions vulnerability.
5
Is there a workaround for CVE-2019-9890 before upgrading?
There are no specific workarounds mentioned for CVE-2019-9890; upgrading to a patched version is recommended.