CVE-2017-12425
No exploitation reported by the sources we read.
- Published2017-08-04
- WeaknessCWE-190
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
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.
Timeline
dates in UTC- 2017-08-0409:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-12425?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-12425?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.0 | = 4.0.1 | no fix published | NVD |
| 4.0 | = 4.0.2 | no fix published | NVD |
| 4.0 | = 4.0.3 | no fix published | NVD |
| 4.0 | = 4.0.4 | no fix published | NVD |
| 5.0 | = 5.0.0 | no fix published | NVD |
| 5.1 | = 5.1.0 | no fix published | NVD |
| 5.1 | = 5.1.1 | no fix published | NVD |
| 5.1 | = 5.1.2 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.1 | = 4.1.0 | no fix published | NVD |
| 4.1 | = 4.1.1 | no fix published | NVD |
| 4.1 | = 4.1.2 | no fix published | NVD |
| 4.1 | = 4.1.3 | no fix published | NVD |
| 4.1 | = 4.1.4 | no fix published | NVD |
| 4.1 | = 4.1.5 | no fix published | NVD |
| 4.1 | = 4.1.6 | no fix published | NVD |
| 4.1 | = 4.1.7 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.0 | = 4.0.2 | no fix published | NVD |
| 4.0 | = 4.0.3 | no fix published | NVD |
| 4.1 | = 4.1.0 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- www.varnish-cache.orgVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.07.5read 2026-10-23
- NVDCVSS 2.05read 2026-10-23
- NVDweakness (CWE)CWE-190read 2026-10-23
- FIRST EPSSEPSS score2.4 %2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2017-08-04
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2017-12425?
Is CVE-2017-12425 actively exploited?
What is the CVSS score for CVE-2017-12425?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.