CVE-2019-15589: GitLab CE/EE vulnerability
Gitlab · GitLab CE/EE
Affected: GitLab CE/EE · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 64% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
An improper access control vulnerability exists in Gitlab <v12.3.2, <v12.2.6, <v12.1.12 which would allow a blocked user would be able to use GIT clone and pull if he had obtained a CI/CD token before.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- GitLab CE/EE12.3.2, 12.2.6, 12.1.12
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Gitlab
- Published
- December 2019
- Bounty reports
- 1 disclosed on HackerOne
Disclosed bug bounty reports about CVE-2019-15589
The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.
- Blocked user Git access through CI/CD tokenGitLab · 2019 · medium severityValid
CoverageNo articles yet
No CyberSIXT article names CVE-2019-15589 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.