What is the severity of CVE-2019-19312?

CVE-2019-19312 has a high severity due to incorrect access control allowing unauthorized information access.

How do I fix CVE-2019-19312?

To fix CVE-2019-19312, upgrade your GitLab EE installation to version 12.5.1 or later.

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.

What type of vulnerability is CVE-2019-19312?

CVE-2019-19312 is classified as an incorrect access control vulnerability.

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.

Vulnerability/
CVE-2019-19312

medium

5.8

5/1/2020

5/8/2024

CVE-2019-19312

First published: Sun Jan 05 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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	>=8.14.0<12.3.8
GitLab	>=12.4.0<12.4.5
GitLab	>=12.5.0<12.5.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-19312?
CVE-2019-19312 has a high severity due to incorrect access control allowing unauthorized information access.
How do I fix CVE-2019-19312?
To fix CVE-2019-19312, upgrade your GitLab EE installation to version 12.5.1 or later.
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.
What type of vulnerability is CVE-2019-19312?
CVE-2019-19312 is classified as an incorrect access control vulnerability.
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.

agent/type
agent/references
agent/severity
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/8.14.0
version/gitlab/12.4.0
version/gitlab/12.5.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2019-19312?
CVE-2019-19312 has a high severity due to incorrect access control allowing unauthorized information access.
How do I fix CVE-2019-19312?
To fix CVE-2019-19312, upgrade your GitLab EE installation to version 12.5.1 or later.
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.
What type of vulnerability is CVE-2019-19312?
CVE-2019-19312 is classified as an incorrect access control vulnerability.
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.