CVE-2017-12425
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of service disruption.
- Exploit odds
- 2.4% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 2.4% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 2.4% · EPSS, next 30 days
- Weakness
- CWE-190 · Integer overflow
- Record status
- Modified
Affected
- varnish-cache Varnish 4.0.2
- varnish-cache Varnish 4.0.3
- Varnish Cache Project Varnish Cache 4.0.1
- Varnish Cache Project Varnish Cache 4.0.2
- Varnish Cache Project Varnish Cache 4.0.3
- Varnish Cache Project Varnish Cache 4.0.4
- varnish-cache Varnish 4.1.0
- varnish-software Varnish Cache 4.1.0
Attack profile CVSS 3.0 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-12425.md and follow it. Check whether this project is affected by CVE-2017-12425. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://www.varnish-cache.org/security/VSV00001.html#vsv00001
- https://www.varnish-cache.org/security/VSV00001.html#vsv00001
References
- http://www.debian.org/security/2017/dsa-3924
- https://bugzilla.redhat.com/show_bug.cgi?id=1477222
- https://bugzilla.suse.com/show_bug.cgi?id=1051917
- https://github.com/varnishcache/varnish-cache/issues/2379
- https://lists.debian.org/debian-security-announce/2017/msg00186.html
- https://www.varnish-cache.org/security/VSV00001.html#vsv00001
- http://www.debian.org/security/2017/dsa-3924
- https://bugzilla.redhat.com/show_bug.cgi?id=1477222
- https://bugzilla.suse.com/show_bug.cgi?id=1051917
- https://github.com/varnishcache/varnish-cache/issues/2379
- https://lists.debian.org/debian-security-announce/2017/msg00186.html
- https://www.varnish-cache.org/security/VSV00001.html#vsv00001