PatchTheCVEvarnish vulnerabilities and fixes
Recent CVEs affecting varnish, with upgrade or downgrade steps. 4 tracked.
varnish has 4 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 2. Most recent: 2017-11-16. Highest priority: CVE-2017-8807 (score 65/100).
- CVE-2017-8807 CRITICAL 9.1 UPGRADE UPGRADE 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.
- CVE-2017-12425 HIGH 7.5 DOWNGRADE DOWNGRADE 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 throu
- CVE-2013-4484 MEDIUM 5.0 DOWNGRADE UPGRADE Varnish before 3.0.5 allows remote attackers to cause a denial of service (child-process crash and temporary c
- CVE-2013-0325 MEDIUM 4.3 DOWNGRADE Multiple cross-site scripting (XSS) vulnerabilities in the Varnish module 6.x-1.x before 6.x-1.2 and 7.x-1.x b
FAQ
How do I fix varnish vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is varnish being exploited right now?
None of the tracked varnish CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which varnish CVE should I patch first?
CVE-2017-8807 currently ranks highest (65/100): 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..