CVE-2019-19312: Medium severity gitlab vulnerability
Published Jan 5, 2020
·Updated
GitLab EE 8.14 through 12.5, 12.4.3, and 12.3.6 has Incorrect Access Control. After a project changed to private, previously forked repositories were still able to get information about the private project through the API.
Affected Software
3 affected components
GitLab GitLab>=8.14.0<12.3.8
GitLab GitLab>=12.4.0<12.4.5
GitLab GitLab>=12.5.0<12.5.2
Event History
Jan 5, 2020
CVE Published
via MITRE·09:37 PM
Data Sourced
via MITRE·09:37 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2019-19312?
CVE-2019-19312 has a high severity due to incorrect access control allowing unauthorized information access.
2
How do I fix CVE-2019-19312?
To fix CVE-2019-19312, upgrade your GitLab EE installation to version 12.5.1 or later.
3
Which versions of GitLab are affected by CVE-2019-19312?
CVE-2019-19312 affects GitLab EE versions from 8.14 to 12.5, 12.4.3, and 12.3.6.
4
What type of vulnerability is CVE-2019-19312?
CVE-2019-19312 is classified as an incorrect access control vulnerability.
5
Can previously forked repositories access private project information due to CVE-2019-19312?
Yes, after a project is changed to private, previously forked repositories can still retrieve information about the private project through the API due to CVE-2019-19312.