varnishcache/varnish-cache
GitHub
CVE History
| CVE | Affected | Published | CVSS v3 | CVSS v2 |
|---|---|---|---|---|
| < 2023-10-10 | 7.5 HIGH | — | ||
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023. | ||||
| >= 6.0.0, < 6.0.8, = 6.0.8, >= 5.0.0, <= 5.2.1, >= 6.1.0, <= 6.6.0, >= 6.0.0, <= 6.0.7, >= 6.0.0, <= 6.0.5 | 6.5 MEDIUM | 6.4 MEDIUM | ||
Varnish Cache, with HTTP/2 enabled, allows request smuggling and VCL authorization bypass via a large Content-Length header for a POST request. This affects Varnish Enterprise 6.0.x before 6.0.8r3, and Varnish Cache 5.x and 6.x before 6.5.2, 6.6.x before 6.6.1, and 6.0 LTS before 6.0.8. | ||||
| >= 6.1.0, < 6.2.2, >= 6.3.0, < 6.3.1, >= 6.0.0, < 6.0.5 | 7.5 HIGH | 5 MEDIUM | ||
An issue was discovered in Varnish Cache before 6.0.5 LTS, 6.1.x and 6.2.x before 6.2.2, and 6.3.x before 6.3.1. It does not clear a pointer between the handling of one client request and the next request within the same connection. This sometimes causes information to be disclosed from the connection workspace, such as data structures associated with previous requests within this connection or VCL-related temporary headers. | ||||
| >= 6.3.0, < 6.3.2, >= 6.1.0, < 6.2.3, >= 6.0.0, < 6.0.6 | 7.5 HIGH | 5 MEDIUM | ||
An issue was discovered in Varnish Cache before 6.0.6 LTS, 6.1.x and 6.2.x before 6.2.3, and 6.3.x before 6.3.2. It occurs when communication with a TLS termination proxy uses PROXY version 2. There can be an assertion failure and daemon restart, which causes a performance loss. | ||||
| >= 5.0.0, < 5.2.1 | 9.1 CRITICAL | 6.4 MEDIUM | ||
vbf_stp_error in bin/varnishd/cache/cache_fetch.c in Varnish HTTP Cache 4.1.x before 4.1.9 and 5.x before 5.2.1 allows remote attackers to obtain sensitive information from process memory because a VFP_GetStorage buffer is larger than intended in certain circumstances involving -sfile Stevedore transient objects. | ||||
| = 4.0.1, = 4.0.4, = 4.0.3, = 4.0.2, = 4.1.0, = 4.1.2, = 4.1.1, = 4.1.4, = 4.1.3, = 4.1.5, = 4.1.6, = 4.1.7, = 5.1.0, = 5.0.0, = 5.1.1, = 5.1.2 | — | 5 MEDIUM | ||
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. | ||||