# CVE-2017-8301: Security feature bypass in n/a

> Attackers can bypass TLS certificate verification in LibreSSL when using specific callback configurations, allowing man-in-the-middle attacks.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-8301, GHSA-phvv-c9gw-v54h

## What is CVE-2017-8301?

CVE-2017-8301 is a medium-severity vulnerability in n/a, published on 27 Apr 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

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

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2017-8301?

It affects 1 product.


Products: Openbsd Libressl.

## How do I fix CVE-2017-8301?

Upgrade to a fixed version.

## Is CVE-2017-8301 being exploited?

There is no known exploitation of CVE-2017-8301 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-35784](https://insights.sbomify.com/CVE-2023-35784/): Use after free in n/a (critical 9.8)
- [CVE-2021-46880](https://insights.sbomify.com/CVE-2021-46880/): Auth bypass in n/a (critical 9.8)
- [CVE-2015-5334](https://insights.sbomify.com/CVE-2015-5334/): Memory corruption in LibreSSL (critical 9.8)
- [CVE-2015-5333](https://insights.sbomify.com/CVE-2015-5333/): Denial of service in LibreSSL (high 7.5)
- [CVE-2014-9424](https://insights.sbomify.com/CVE-2014-9424/): Use after free in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8301 and fix it if it is affected.

What it is: CVE-2017-8301 is a medium-severity vulnerability in n/a, published on 27 Apr 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-8301 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-8301/ (Markdown: https://insights.sbomify.com/CVE-2017-8301/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-8301
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-8301
- OSV: https://osv.dev/vulnerability/CVE-2017-8301

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-8301/
Summaries are generated and may contain mistakes; the official description above is the record.