What is the severity of CVE-2017-17716?

CVE-2017-17716 is classified as a medium severity vulnerability due to potential unauthorized access risks.

How do I fix CVE-2017-17716?

To fix CVE-2017-17716, upgrade GitLab to version 9.4.2 or later which includes LDAP SSL certificate verification support.

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

CVE-2017-17716 affects GitLab versions 9.4.0 and 9.4.1.

What does CVE-2017-17716 imply for LDAP connections?

CVE-2017-17716 implies that LDAP connections on affected versions do not validate SSL certificates, which could expose users to man-in-the-middle attacks.

Is there a workaround for CVE-2017-17716?

There are no documented workarounds for CVE-2017-17716, so it is recommended to update to a patched version.

Vulnerability/
CVE-2017-17716

medium

5.9

CWE

295

17/12/2017

16/9/2024

CVE-2017-17716

First published: Sun Dec 17 2017(Updated: )

GitLab 9.4.x before 9.4.2 does not support LDAP SSL certificate verification, but a verify_certificates LDAP option was mentioned in the 9.4 release announcement. This issue occurred because code was not merged. This is related to use of the omniauth-ldap library and the gitlab_omniauth-ldap gem.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
GitLab	=9.4.0
GitLab	=9.4.0-rc1
GitLab	=9.4.0-rc2
GitLab	=9.4.0-rc3
GitLab	=9.4.0-rc4
GitLab	=9.4.0-rc5
GitLab	=9.4.0-rc6
GitLab	=9.4.1

Remedy

https://gitlab.com/gitlab-org/gitlab-ce/issues/30420

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-17716?
CVE-2017-17716 is classified as a medium severity vulnerability due to potential unauthorized access risks.
How do I fix CVE-2017-17716?
To fix CVE-2017-17716, upgrade GitLab to version 9.4.2 or later which includes LDAP SSL certificate verification support.
What versions of GitLab are affected by CVE-2017-17716?
CVE-2017-17716 affects GitLab versions 9.4.0 and 9.4.1.
What does CVE-2017-17716 imply for LDAP connections?
CVE-2017-17716 implies that LDAP connections on affected versions do not validate SSL certificates, which could expose users to man-in-the-middle attacks.
Is there a workaround for CVE-2017-17716?
There are no documented workarounds for CVE-2017-17716, so it is recommended to update to a patched version.

agent/type
agent/references
agent/severity
agent/remedy
agent/author
agent/weakness
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/9.4.0
version/gitlab/9.4.0-rc1
version/gitlab/9.4.0-rc2
version/gitlab/9.4.0-rc3
version/gitlab/9.4.0-rc4
version/gitlab/9.4.0-rc5
version/gitlab/9.4.0-rc6
version/gitlab/9.4.1

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-17716?
CVE-2017-17716 is classified as a medium severity vulnerability due to potential unauthorized access risks.
How do I fix CVE-2017-17716?
To fix CVE-2017-17716, upgrade GitLab to version 9.4.2 or later which includes LDAP SSL certificate verification support.
What versions of GitLab are affected by CVE-2017-17716?
CVE-2017-17716 affects GitLab versions 9.4.0 and 9.4.1.
What does CVE-2017-17716 imply for LDAP connections?
CVE-2017-17716 implies that LDAP connections on affected versions do not validate SSL certificates, which could expose users to man-in-the-middle attacks.
Is there a workaround for CVE-2017-17716?
There are no documented workarounds for CVE-2017-17716, so it is recommended to update to a patched version.