https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 01:49:16 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-257151 EUVD-2026-257151 https://cve.radiocsirt.org/vuln/euvd-2026-257151 https://cve.radiocsirt.org/vuln/fkie_cve-2025-27093 <p>Sliver is a command and control framework that uses a custom Wireguard netstack. In versions 1.5.43 and earlier, and in development version 1.6.0-dev, the netstack does not limit traffic between Wireguard clients. This allows clients to communicate with each other unrestrictedly, potentially enabling leaked or recovered keypairs to be used to attack operators or allowing port forwardings to be accessible from other implants.</p> <p>Sliver is a command and control framework that uses a custom Wireguard netstack. In versions 1.5.43 and earlier, and in development version 1.6.0-dev, the netstack does not limit traffic between Wireguard clients. This allows clients to communicate with each other unrestrictedly, potentially enabling leaked or recovered keypairs to be used to attack operators or allowing port forwardings to be accessible from other implants.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-27093 https://cve.radiocsirt.org/vuln/ghsa-q8j9-34qf-7vq7 <p><strong>Affected:</strong> Go: github.com/BishopFox/sliver</p> <p>### Summary Sliver&#39;s custom Wireguard netstack doesn&#39;t limit traffic between Wireguard clients, this could lead to: 1. Leaked/recovered keypair (from a beacon) being used to attack operators. 2. Port forwardings usable from other implants.</p> <p>### Details 1. Sliver treat operators&#39; Wireguard config and beacon/session&#39;s Wireguard config equally, they both connect to the wireguard listener created from the CLI.</p> <p>2. The current netstack implementation does not filter traffic between clients. 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&#39;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(&#34;Envelope marshaling error: %v&#34;, 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:</p> <p>``` 3. The docs says to use a Wireguard clients and operator wg-config to connect to the same WG listener as beacons: https://sliver.sh/docs?name=Port%20Forwarding</p> <p>4. If the operator uses official wireguard clients that integrates with the OS&#39;s netstack (I&#39;m using the [Windows client](https://www.wireguard.com/install/)) then thei…</p> <p><strong>Affected:</strong> Go: github.com/BishopFox/sliver</p> <p>### Summary Sliver&#39;s custom Wireguard netstack doesn&#39;t limit traffic between Wireguard clients, this could lead to: 1. Leaked/recovered keypair (from a beacon) being used to attack operators. 2. Port forwardings usable from other implants.</p> <p>### Details 1. Sliver treat operators&#39; Wireguard config and beacon/session&#39;s Wireguard config equally, they both connect to the wireguard listener created from the CLI.</p> <p>2. The current netstack implementation does not filter traffic between clients. 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&#39;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(&#34;Envelope marshaling error: %v&#34;, 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:</p> <p>``` 3. The docs says to use a Wireguard clients and operator wg-config to connect to the same WG listener as beacons: https://sliver.sh/docs?name=Port%20Forwarding</p> <p>4. If the operator uses official wireguard clients that integrates with the OS&#39;s netstack (I&#39;m using the [Windows client](https://www.wireguard.com/install/)) then thei…</p> https://cve.radiocsirt.org/vuln/ghsa-q8j9-34qf-7vq7 https://cve.radiocsirt.org/vuln/opensuse-su-2025:15710-1 <p>govulncheck-vulndb-0.0.20251105T184115-1.1 on GA media</p> <p>govulncheck-vulndb-0.0.20251105T184115-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:15710-1