Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2023-34758

HIGH

CVE-2023-34758 is a high-severity (CVSS 8.1) Broken Cryptographic Algorithm vulnerability in github.com/bishopfox/sliver. O3 Security confirms whether CVE-2023-34758 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Silver vulnerable to MitM attack against implants due to a cryptography vulnerability

Also known asCVE-2023-35170GHSA-8jxm-xp43-qh3qGO-2023-1866
Published
Aug 28, 2023
Updated
Jul 15, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected
🐹github.com/bishopfox/sliver

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Sliver from v1.5.x to v1.5.39 has an improper cryptographic implementation, which allows attackers to execute a man-in-the-middle attack via intercepted and crafted responses.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/bishopfox/sliver1.5.0&&< 1.5.401.5.40

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bishopfox/sliver. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/bishopfox/sliver to 1.5.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-34758 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-34758 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2023-34758. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Sliver from v1.5.x to v1.5.39 has an improper cryptographic implementation, which allows attackers to execute a man-in-the-middle attack via intercepted and crafted responses.
O3 Security · Impact-Aware SCA

Is CVE-2023-34758 in your dependencies?

O3 detects CVE-2023-34758 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.