Code execution via recoverable KEM session keys
Published Aug 28, 2023 · Updated Oct 2, 2024
Cryptographic failure in Bishop Fox Sliver 1.5.0 through 1.5.39 allows man-in-the-middle attackers to execute code on implants. The Sliver Key Encapsulation Mechanism derives a reusable shared secret from the server public key and implant private key embedded in each implant, allowing recovery of session keys and forgery of encrypted command-and-control messages. Exploitation requires interception of an HTTP or DNS implant channel and a copy of the corresponding implant binary; mTLS and WireGuard transports are not affected.
Summary
What happened
Cryptographic failure in Bishop Fox Sliver 1.5.0 through 1.5.39 allows man-in-the-middle attackers to execute code on implants. The Sliver Key Encapsulation Mechanism derives a reusable shared secret from the server public key and implant private key embedded in each implant, allowing recovery of session keys and forgery of encrypted command-and-control messages. Exploitation requires interception of an HTTP or DNS implant channel and a copy of the corresponding implant binary; mTLS and WireGuard transports are not affected.
The record
- CVE
- CVE-2023-34758
- Published
- Aug 28, 2023
- Updated
- Oct 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-327, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2023CVE publishedPublication date reported by the CVE source.
- Oct 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Slivjackerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo