GHSA-2phg-qgmm-r638: Sliver has Potential Zip Bomb Denial of Service in GzipEncoder
Summary GzipEncoder does not limit output size when processing compressed data. This allows unauthenticated remote attackers to crash sliver server by sending a http request with highly compressed gzip data (aka zip bomb). Details In util/encoders/gzip.go, Decode() method decompresses given data by reading the entire gzip buffer at once without limiting output size.
Published Feb 25, 2026 · Updated Feb 27, 2026
Affected packages
github.com/BishopFox/sliver
- Ecosystem
- Go
- Affected
- < 1.7.2
- Fixed in
- 1.7.2
- Check
go list -m github.com/BishopFox/sliver
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
GzipEncoder does not limit output size when processing compressed data. This allows unauthenticated remote attackers to crash sliver server by sending a http request with highly compressed gzip data (aka zip bomb).
Details
In util/encoders/gzip.go, Decode() method decompresses given data by reading the entire gzip buffer at once without limiting output size.
PoC
data = gzip.compress(bytes(1024 * 1024 * 1024)) * 16
requests.post(f"http://172.17.0.2/{nonce}", data=data)Impact
Unauthenticated remote attackers can exhaust memory and cpu resource of sliver server and crash it when they have GzipEncoderID, which can be easily retrived from implant's http traffic, or by brute-forcing.
A fixed version is available at https://github.com/BishopFox/sliver/releases/tag/v1.7.2.
Credited to Cycloctane.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
