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.
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.
- Published
- Aug 4, 2017
- Updated
- Jun 16, 2026
- EPSS
- 2.4% · 84th percentile
- CWE
- CWE-190
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.4%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| varnish-cache | varnish | cpe:2.3:a:varnish-cache:varnish |
| varnish cache project | varnish cache | cpe:2.3:a:varnish_cache_project:varnish_cache |
| varnish-software | varnish cache | cpe:2.3:a:varnish-software:varnish_cache |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- varnish cache project varnish cache4.0.1
- varnish cache project varnish cache4.0.2
- varnish cache project varnish cache4.0.3
- varnish cache project varnish cache4.0.4
- varnish cache project varnish cache5.0.0
- varnish cache project varnish cache5.1.0
- varnish cache project varnish cache5.1.1
- varnish cache project varnish cache5.1.2
- varnish-cache varnish4.0.2
- varnish-cache varnish4.0.3
- varnish-cache varnish4.1.0
- varnish-software varnish cache4.1.0
- varnish-software varnish cache4.1.1
- varnish-software varnish cache4.1.2
- varnish-software varnish cache4.1.3
- varnish-software varnish cache4.1.4
- varnish-software varnish cache4.1.5
- varnish-software varnish cache4.1.6
- varnish-software varnish cache4.1.7
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | varnish | before 5.1.3-r0 | 5.1.3-r0 |
| Alpine:v3.3 | varnish | before 4.1.2-r2 | 4.1.2-r2 |
| Alpine:v3.4 | varnish | before 4.1.2-r4 | 4.1.2-r4 |
| Alpine:v3.5 | varnish | before 4.1.3-r1 | 4.1.3-r1 |
| Debian:12 | varnish | before 5.0.0-7.1 | 5.0.0-7.1 |
| Debian:8 | varnish | before 4.0.2-1+deb8u1 | 4.0.2-1+deb8u1 |
| Debian:9 | varnish | before 5.0.0-7+deb9u1 | 5.0.0-7+deb9u1 |
Same product
varnish-cache: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-8807vbf_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.1 allows remote attackers to o37Monitor
- CVE-2013-4484Varnish before 3.0.5 allows remote attackers to cause a denial of service (child-process crash and temporary caching outage) via a GET reque21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:varnish | 5.1.3-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:varnish | 5.0.0-7.1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- www.debian.org/security/2017/dsa-3924
- bugzilla.redhat.com/show_bug.cgi?id=1477222
- bugzilla.suse.com/show_bug.cgi?id=1051917
- github.com/varnishcache/varnish-cache/issues/2379
- lists.debian.org/debian-security-announce/2017/msg00186.html
- www.varnish-cache.org/security/VSV00001.html#vsv00001
Vendor advisories and official records. Exploit/PoC links are deliberately left out.