Categories
CVE-2023-34758

Vulnerability in github.com/bishopfox/sliver (CVE-2023-34758)

Summary

Vulnerability in github.com/bishopfox/sliver (CVE-2023-34758). Successful exploitation can lead to full system takeover. Exploitable via notepad.exe. Mitigation: upgrade to 1.5.40 or later.

Original description

The description as published by the source.

Summary

The current cryptography implementation in Sliver up to version 1.5.39 allows a MitM with access to the corresponding implant binary to execute arbitrary codes on implanted devices via intercepted and crafted responses. (Reserved CVE ID: CVE-2023-34758)

Details

Please see the PoC repo.

PoC

Please also see the PoC repo.
To setup a simple PoC environment,

  1. Generate an implant with its C2 set to the PoC server's address and copy the embedded private implant key and public server key into the config json.
  2. Run the implant on a separate VM and a notepad.exe window should pop up on the implanted VM.

Impact

A successful attack grants the attacker permission to execute arbitrary code on the implanted device.

References

https://github.com/BishopFox/sliver/blob/master/implant/sliver/cryptography/implant.go
https://github.com/BishopFox/sliver/blob/master/implant/sliver/cryptography/crypto.go
https://github.com/tangent65536/Slivjacker

Credits

Ting-Wei Hsieh from CHT Security Co. Ltd.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2023-34758 has been found in github.com/bishopfox/sliver.
Attackers can target a specific entry point like notepad.exe over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade github.com/bishopfox/sliver to 1.5.40 or later.
If unsure, ask your IT team or search "github.com/bishopfox/sliver CVE-2023-34758" on the vendor's site.

CVE-2023-34758 (github.com/bishopfox/sliver) — CWE-327
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: notepad.exe
Patched: 1.5.40 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-327) exists in github.com/bishopfox/sliver. Attackers reach the vulnerable code path via notepad.exe without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/bishopfox/sliver. Attack surface: notepad.exe.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.5.40.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/bishopfox/sliver' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'github.com/bishopfox/sliver' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/bishopfox/sliver を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/bishopfox/sliver to 1.5.40

    ステージング環境で 1.5.40 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/bishopfox/sliver
[{"type":"SEMVER","events":[{"introduced":"1.5.0"},{"fixed":"1.5.40"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details