CVE-2017-0926: High severity gitlab vulnerability
Published Mar 21, 2018
·Updated
Gitlab Community Edition version 10.3 is vulnerable to an improper authorization issue in the Oauth sign-in component resulting in unauthorized user login.
Affected Software
10 affected componentsFixes available
debian/gitlab
16.0.8+ds1-2
GitLab GitLab>=8.8.0<=9.5.10
GitLab GitLab>=8.8.0<=9.5.10
GitLab GitLab>=10.0.0<=10.1.5
GitLab GitLab>=10.0.0<=10.1.5
GitLab GitLab>=10.2.0<=10.2.5
GitLab GitLab>=10.2.0<=10.2.5
GitLab GitLab>=10.3.0<=10.3.3
GitLab GitLab>=10.3.0<=10.3.3
Debian Debian Linux=9.0
Event History
Mar 21, 2018
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2017-0926?
CVE-2017-0926 is classified as a high severity vulnerability due to its potential to allow unauthorized user login.
2
How do I fix CVE-2017-0926?
To fix CVE-2017-0926, upgrade GitLab to version 10.3.4 or later.
3
Which versions of GitLab are affected by CVE-2017-0926?
CVE-2017-0926 affects GitLab versions 8.8.0 through 10.3.3.
4
What kind of issue does CVE-2017-0926 represent?
CVE-2017-0926 represents an improper authorization issue in the OAuth sign-in component of GitLab.
5
Is there a workaround for CVE-2017-0926?
There is no official workaround for CVE-2017-0926, and it is recommended to upgrade to a fixed version.