Sliver denial of service in PNG-encoded HTTP listeners
BishopFox sliver
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/BishopFox/sliver Go |
|
|
| github.com/bishopfox/sliver Go |
|
|
BishopFox sliver
| Product | Affected | Fixed in |
|---|---|---|
| github.com/BishopFox/sliver Go |
|
|
| github.com/bishopfox/sliver Go |
|
|
Sliver is a command and control framework. Prior to 1.7.6, an HTTP(S) listener using the PNG encoder accepts attacker-controlled PNG dimensions without an effective decoded-size or pixel limit in util/encoders/images.go, while the listener nonce space implemented in server/encoders/encoders.go is small enough to search remotely. An unauthenticated attacker who identifies a valid nonce can submit a highly compressed image to PNGEncoder.Decode, where it expands during png.Decode, exhausting server memory and causing a complete loss of availability. This vulnerability is fixed in 1.7.6.
From the CVE record · GitHub_M
Before 1.7.6, Sliver's HTTP(S) listener with the PNG encoder does not effectively limit decoded image size or pixels. An unauthenticated remote attacker who finds a valid listener nonce can submit a compressed PNG that exhausts server memory and causes a complete loss of availability.
Check deployments using the PNG encoder in Sliver HTTP(S) listeners and Go packages github.com/BishopFox/sliver or github.com/bishopfox/sliver at versions earlier than 1.7.6.