CVE-2017-8301
First published: Thu Apr 27 2017(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| OpenBSD LibreSSL | =2.5.1 | |
| OpenBSD LibreSSL | =2.5.2 | |
| OpenBSD LibreSSL | =2.5.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-8301?
CVE-2017-8301 has a moderate severity level due to the potential for accepting invalid TLS certificates.
How do I fix CVE-2017-8301?
To fix CVE-2017-8301, upgrade LibreSSL to version 2.5.4 or later to ensure proper TLS certificate verification.
Which versions of LibreSSL are affected by CVE-2017-8301?
CVE-2017-8301 affects LibreSSL versions 2.5.1, 2.5.2, and 2.5.3.
What is the impact of CVE-2017-8301?
The impact of CVE-2017-8301 includes potential exposure to man-in-the-middle attacks by accepting invalid certificates.
Is CVE-2017-8301 relevant for nginx users?
Yes, CVE-2017-8301 is particularly relevant for nginx users who rely on user-provided verification callbacks.
- agent/references
- agent/softwarecombine
- agent/remedy
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/openbsd
- canonical/openbsd libressl
- version/openbsd libressl/2.5.1
- version/openbsd libressl/2.5.2
- version/openbsd libressl/2.5.3