CVE-2017-12425
Varnish-cache Varnish vulnerability
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.
Affected products
Varnish, Varnish Cache. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Varnish-cache Varnish runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- www.varnish-cache.org/security/VSV00001.html#vsv00001 · Vendor Advisory
- bugzilla.redhat.com/show_bug.cgi?id=1477222 · Third Party Advisory
- bugzilla.suse.com/show_bug.cgi?id=1051917 · Third Party Advisory
- github.com/varnishcache/varnish-cache/issues/2379 · Third Party Advisory
- lists.debian.org/debian-security-announce/2017/msg00186.html · Third Party Advisory
- www.debian.org/security/2017/dsa-3924
- nvd.nist.gov/vuln/detail/CVE-2017-12425
- cve.org/CVERecord?id=CVE-2017-12425
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.