What is the severity of CVE-2017-0921?

CVE-2017-0921 has been classified as a high severity vulnerability due to the potential for account takeover if a session is compromised.

How do I fix CVE-2017-0921?

To fix CVE-2017-0921, upgrade your GitLab installation to version 10.1.6, 10.2.6, or 10.3.4 or later.

What versions of GitLab are affected by CVE-2017-0921?

CVE-2017-0921 affects GitLab Community and Enterprise Editions prior to version 10.1.6, 10.2.6, and 10.3.4.

What component does CVE-2017-0921 affect?

CVE-2017-0921 affects the PasswordsController component in GitLab.

What are the potential impacts of CVE-2017-0921?

The potential impact of CVE-2017-0921 includes unauthorized account access and account takeover.

Vulnerability/
CVE-2017-0921

high

8.1

CWE

640

24/5/2018

5/8/2024

CVE-2017-0921

First published: Thu May 24 2018(Updated: )

GitLab Community and Enterprise Editions before 10.1.6, 10.2.6, and 10.3.4 are vulnerable to an unverified password change issue in the PasswordsController component resulting in potential account takeover if a victim's session is compromised.

Credit: support@hackerone.com

Affected Software	Affected Version	How to fix
GitLab	<10.1.6
GitLab	<10.1.6
GitLab	>=10.2.0<10.2.6
GitLab	>=10.2.0<10.2.6
GitLab	>=10.3.0<10.3.4
GitLab	>=10.3.0<10.3.4

Never miss a vulnerability like this again

Reference Links

https://about.gitlab.com/2018/05/29/security-release-gitlab-10-dot-8-dot-2-released/

Frequently Asked Questions

What is the severity of CVE-2017-0921?
CVE-2017-0921 has been classified as a high severity vulnerability due to the potential for account takeover if a session is compromised.
How do I fix CVE-2017-0921?
To fix CVE-2017-0921, upgrade your GitLab installation to version 10.1.6, 10.2.6, or 10.3.4 or later.
What versions of GitLab are affected by CVE-2017-0921?
CVE-2017-0921 affects GitLab Community and Enterprise Editions prior to version 10.1.6, 10.2.6, and 10.3.4.
What component does CVE-2017-0921 affect?
CVE-2017-0921 affects the PasswordsController component in GitLab.
What are the potential impacts of CVE-2017-0921?
The potential impact of CVE-2017-0921 includes unauthorized account access and account takeover.

agent/type
agent/references
agent/author
agent/weakness
agent/severity
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/10.2.0
version/gitlab/10.3.0

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-0921?
CVE-2017-0921 has been classified as a high severity vulnerability due to the potential for account takeover if a session is compromised.
How do I fix CVE-2017-0921?
To fix CVE-2017-0921, upgrade your GitLab installation to version 10.1.6, 10.2.6, or 10.3.4 or later.
What versions of GitLab are affected by CVE-2017-0921?
CVE-2017-0921 affects GitLab Community and Enterprise Editions prior to version 10.1.6, 10.2.6, and 10.3.4.
What component does CVE-2017-0921 affect?
CVE-2017-0921 affects the PasswordsController component in GitLab.
What are the potential impacts of CVE-2017-0921?
The potential impact of CVE-2017-0921 includes unauthorized account access and account takeover.