CVE-2017-17716 Security feature bypass in n/a
GitLab fails to verify LDAP SSL certificates despite documentation, allowing potential man-in-the-middle attacks if LDAP is configured.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2017-17716?
CVE-2017-17716 is a medium-severity vulnerability in Gitlab Gitlab, published on 17 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-295
Which versions are affected by CVE-2017-17716?
It affects 1 product.
Products include Gitlab Gitlab.
How do I fix CVE-2017-17716?
No fix has been published for CVE-2017-17716 yet. Limit exposure of the affected software until one is available.
Is CVE-2017-17716 being exploited?
There is no known exploitation of CVE-2017-17716 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as GHSA-3493-8hqx-h937.