github.com/BishopFox/sliver
Affected
- introduced
0, fixed1.5.44(semver)
Fixed versions
1.5.44
Fix
- Fixed version
1.5.44go get github.com/BishopFox/[email protected]
Advisory
Also known as: CVE-2025-27093, GO-2025-4079
Silver has unrestricted traffic between Wireguard clients
Summary
Sliver's custom Wireguard netstack doesn't limit traffic between Wireguard clients, this could lead to:
Details
I think this piece of code handle traffic between clients, from experimental results clients can ping and connect to each other freely, and I didn't see any filtering here either:
File: server\c2\wireguard.go
246: func socketWGWriteEnvelope(connection net.Conn, envelope *sliverpb.Envelope) error {
247: data, err := proto.Marshal(envelope)
248: if err != nil {
249: wgLog.Errorf("Envelope marshaling error: %v", err)
250: return err
251: }
252: dataLengthBuf := new(bytes.Buffer)
253: binary.Write(dataLengthBuf, binary.LittleEndian, uint32(len(data)))
254: connection.Write(dataLengthBuf.Bytes())
255: connection.Write(data)
256: return nil
257: }
258:
https://sliver.sh/docs?name=Port%20Forwarding
PoC
Easy way:
Slightly complicated way:
Impact
The operator's machine is impacted, if their services contain a vulnerability, an attacker can exploit it and gain RCE. If not then it could be used to gather information (Hostname, SSH signature, etc).
Suggestion
Vulnerable versions
All versions containing wireguard functionality.
Medium Basis: The source's own band: MODERATE
0, fixed 1.5.44 (semver)1.5.44
1.5.44go get github.com/BishopFox/[email protected]0, fixed 1.5.44 (semver)1.5.44
1.5.44go get github.com/bishopfox/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0