CVE-2019-19312
Summary
| CVE | CVE-2019-19312 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2020-01-05 22:15:00 UTC |
| Updated | 2021-07-21 11:39:00 UTC |
| Description | 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. |
Risk And Classification
Problem Types: NVD-CWE-noinfo
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| GitLab Security Release: 12.5.1, 12.4.4, and 12.3.7 | GitLab | CONFIRM | about.gitlab.com | Vendor Advisory |
| Releases | GitLab | MISC | about.gitlab.com | Release Notes |
| Forked Project's Information is Still Being Disclosed in Project API after being changed to Private (#28802) · Issues · GitLab.org / GitLab · GitLab | MISC | gitlab.com | Broken Link |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.