What is the severity of CVE-2017-0927?

CVE-2017-0927 is rated as a medium severity vulnerability due to improper authorization issues.

How do I fix CVE-2017-0927?

To fix CVE-2017-0927, upgrade GitLab to version 10.3.4 or later.

Who is affected by CVE-2017-0927?

CVE-2017-0927 affects versions of GitLab Community and Enterprise Edition from 8.16.0 to 10.3.3.

What type of vulnerability is CVE-2017-0927?

CVE-2017-0927 is an improper authorization vulnerability in the deployment keys component.

Can guest users exploit CVE-2017-0927?

Yes, guest users can potentially exploit CVE-2017-0927 to access unauthorized deployment keys.

Vulnerability/
CVE-2017-0927

medium

6.5

CWE

863 285

21/3/2018

5/8/2024

CVE-2017-0927

First published: Wed Mar 21 2018(Updated: )

Gitlab Community Edition version 10.3 is vulnerable to an improper authorization issue in the deployment keys component resulting in unauthorized use of deployment keys by guest users.

Credit: support@hackerone.com

Affected Software	Affected Version	How to fix
GitLab	>=8.16.0<=9.5.10
GitLab	>=8.16.0<=9.5.10
GitLab	>=10.0.0<=10.1.5
GitLab	>=10.0.0<=10.1.5
GitLab	>=10.2.0<=10.2.5
GitLab	>=10.2.0<=10.2.5
GitLab	>=10.3.0<=10.3.3
GitLab	>=10.3.0<=10.3.3

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-0927?
CVE-2017-0927 is rated as a medium severity vulnerability due to improper authorization issues.
How do I fix CVE-2017-0927?
To fix CVE-2017-0927, upgrade GitLab to version 10.3.4 or later.
Who is affected by CVE-2017-0927?
CVE-2017-0927 affects versions of GitLab Community and Enterprise Edition from 8.16.0 to 10.3.3.
What type of vulnerability is CVE-2017-0927?
CVE-2017-0927 is an improper authorization vulnerability in the deployment keys component.
Can guest users exploit CVE-2017-0927?
Yes, guest users can potentially exploit CVE-2017-0927 to access unauthorized deployment keys.

agent/references
agent/weakness
agent/type
agent/severity
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/8.16.0
version/gitlab/9.5.10
version/gitlab/10.0.0
version/gitlab/10.1.5
version/gitlab/10.2.0
version/gitlab/10.2.5
version/gitlab/10.3.0
version/gitlab/10.3.3

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2017-0927?
CVE-2017-0927 is rated as a medium severity vulnerability due to improper authorization issues.
How do I fix CVE-2017-0927?
To fix CVE-2017-0927, upgrade GitLab to version 10.3.4 or later.
Who is affected by CVE-2017-0927?
CVE-2017-0927 affects versions of GitLab Community and Enterprise Edition from 8.16.0 to 10.3.3.
What type of vulnerability is CVE-2017-0927?
CVE-2017-0927 is an improper authorization vulnerability in the deployment keys component.
Can guest users exploit CVE-2017-0927?
Yes, guest users can potentially exploit CVE-2017-0927 to access unauthorized deployment keys.