Varnish Enterprise before 6.0.13r13 allows remote attackers to obtain sensitive information via an out-of-bounds read for range requests on ephemeral MSE4 stevedore objects.
End of life: 3/15/2025, Latest version: 7.5.0
End of life: 3/15/2025, Latest version: 7.5.0
End of life: 9/15/2024, Latest version: 7.4.3
End of life: 9/15/2024, Latest version: 7.4.3
End of life: 3/15/2024, Latest version: 7.3.2
End of life: 3/15/2024, Latest version: 7.3.2
End of life: 9/15/2023, Latest version: 7.2.1
End of life: 9/15/2023, Latest version: 7.2.1
End of life: 3/15/2023, Latest version: 7.1.2
End of life: 3/15/2023, Latest version: 7.1.2
End of life: 9/15/2022, Latest version: 7.0.3
End of life: 9/15/2022, Latest version: 7.0.3
An issue was discovered in Varnish HTTP Cache 4.0.1 through 4.0.4, 4.1.0 through 4.1.7, 5.0.0, and 5.1.0 through 5.1.2. A wrong if statement in the varnishd source code means that particular invalid requests from the client can trigger an assert, related to an Integer Overflow. This causes the varnishd worker process to abort and restart, losing the cached contents in the process. An attacker can therefore crash the varnishd worker process on demand and effectively keep it from serving content - a Denial-of-Service attack. The specific source-code filename containing the incorrect statement varies across releases.
Varnish before 3.0.5 allows remote attackers to cause a denial of service (child-process crash and temporary caching outage) via a GET request with trailing whitespace characters and no URI.