aboutsummaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorkoobs <koobs@FreeBSD.org>2014-01-25 17:24:38 +0800
committerkoobs <koobs@FreeBSD.org>2014-01-25 17:24:38 +0800
commit70b325d03f4c6f97baba7e9dd15a843ab9f1aa3f (patch)
tree2f7f7bb55322042f141d4fa070bd89c2418f8453 /security
parentcf1583e5a6912c37ec1fbb5f614c57cca78e38c3 (diff)
downloadfreebsd-ports-gnome-70b325d03f4c6f97baba7e9dd15a843ab9f1aa3f.tar.gz
freebsd-ports-gnome-70b325d03f4c6f97baba7e9dd15a843ab9f1aa3f.tar.zst
freebsd-ports-gnome-70b325d03f4c6f97baba7e9dd15a843ab9f1aa3f.zip
Document Varnish HTTP Cache < 3.0.5 DoS Vulnerability
Reviewed by: remko
Diffstat (limited to 'security')
-rw-r--r--security/vuxml/vuln.xml46
1 files changed, 46 insertions, 0 deletions
diff --git a/security/vuxml/vuln.xml b/security/vuxml/vuln.xml
index 0a0419e63e10..cbdcd3b5e757 100644
--- a/security/vuxml/vuln.xml
+++ b/security/vuxml/vuln.xml
@@ -51,6 +51,52 @@ Note: Please add new entries to the beginning of this file.
-->
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
+ <vuln vid="d9dbe6e8-84da-11e3-98bd-080027f2d077">
+ <topic>varnish -- DoS vulnerability in Varnish HTTP cache</topic>
+ <affects>
+ <package>
+ <name>varnish</name>
+ <range><lt>3.0.5</lt></range>
+ </package>
+ </affects>
+ <description>
+ <body xmlns="http://www.w3.org/1999/xhtml">
+ <p>Varnish Cache Project reports:</p>
+ <blockquote cite="https://www.varnish-cache.org/lists/pipermail/varnish-announce/2013-October/000686.html">
+ <p>If Varnish receives a certain illegal request, and the subroutine
+ 'vcl_error{}' restarts the request, the varnishd worker process
+ will crash with an assert.
+ </p>
+ <p>The varnishd management process will restart the worker process, but
+ there will be a brief interruption of service and the cache will be
+ emptied, causing more traffic to go to the backend.
+ </p>
+ <p>We are releasing this advisory because restarting from vcl_error{} is both fairly common and documented.</p>
+ <p>This is purely a denial of service vulnerability, there is no risk of privilege escalation.</p>
+ <p>Workaround</p>
+ <p>Insert this at the top of your VCL file:</p>
+ <pre>
+ sub vcl_error {
+ if (obj.status == 400 || obj.status == 413) {
+ return(deliver);
+ }
+ }
+
+ Or add this test at the top of your existing vcl_error{}.
+ </pre>
+ </blockquote>
+ </body>
+ </description>
+ <references>
+ <cvename>CVE-2013-4484</cvename>
+ <mlist>https://www.varnish-cache.org/lists/pipermail/varnish-announce/2013-October/000686.html</mlist>
+ </references>
+ <dates>
+ <discovery>2013-10-30</discovery>
+ <entry>2014-01-25</entry>
+ </dates>
+ </vuln>
+
<vuln vid="c0ef849e-84ac-11e3-bec4-9c4e36909cc0">
<topic>linux-flashplugin -- multiple vulnerabilities</topic>
<affects>