CVE-2019-19312 Missing authorization in n/a
Attackers can access private project information via API if the project was previously forked, exposing sensitive data in GitLab EE.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2019-19312?
CVE-2019-19312 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 5 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Which versions are affected by CVE-2019-19312?
It affects 1 product.
Products include Gitlab Gitlab.
How do I fix CVE-2019-19312?
No fix has been published for CVE-2019-19312 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2019-19312 being exploited?
There is no known exploitation of CVE-2019-19312 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as GHSA-6955-m4p2-35rh.