CVE-2017-0919: Gitlab vulnerability
Affected: Gitlab · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 65% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
GitLab Community and Enterprise Editions before 10.1.6, 10.2.6, and 10.3.4 are vulnerable to an authorization bypass issue in the GitLab import component resulting in an attacker being able to perform operations under a group in which they were previously unauthorized.
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
- July 2018
- Bounty reports
- 1 disclosed on HackerOne
Disclosed bug bounty reports about CVE-2017-0919
The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.
- GitHub import allows user to create child group under existing namespaceGitLab · 2018 · high severityValid
CoverageNo articles yet
No CyberSIXT article names CVE-2017-0919 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.