CVE-2019-19312 json
GitLab EE 8.14 through 12.5, 12.4.3, and 12.3.6 has Incorrect Access Control.
published 6y ago modified 4mo ago also EUVD-2019-8936
- cvss
- 5.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- gitlab gitlab 12.3.8, 12.4.5, 12.5.2
Is CVE-2019-19312 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.08% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Technology feeds
References
-
about.gitlab.com
/blog/2019/11/27/security-release-gitlab-12-5-1-released/
vendor-advisory
-
about.gitlab.com
/blog/categories/releases/
release-notes
-
gitlab.com
/gitlab-org/gitlab/issues/28802
broken-link
Sources
- CVE List CVE-2019-19312
- NVD CVE-2019-19312
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.