CVE-2017-12425

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: 2017-08-04 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-12425 is rated Moderate Risk (58.7/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.42%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-12425

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-29 1.05% 1.42% +0.37%
2 2025-12-18 0.83% 1.05% +0.22%
3 2025-03-30 — 0.83% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-12425

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2017-12425

OS Trackers for CVE-2017-12425

vendor priority summary link
alpine — CVE-2017-12425: 1 source package rows (varnish); 10 state rows across 10 repos (3.10-main, 3.11-main, 3.12-main, 3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 10, open 0. https://security.alpinelinux.org/vuln/CVE-2017-12425
debian not yet assigned CVE-2017-12425 not yet assigned priority: Debian including 1 source packages (varnish), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2017-12425
redhat medium — https://access.redhat.com/security/cve/CVE-2017-12425
ubuntu medium CVE-2017-12425 medium priority: Ubuntu including 1 source packages (varnish), 4 status rows across 4 suites (trusty, upstream, xenial, zesty): released 3, not-affected 1. https://ubuntu.com/security/CVE-2017-12425

Affected software / configurations for CVE-2017-12425

Vendor Product Version Raw CPE
varnish-cache varnish 4.0.2 cpe:2.3:a:varnish-cache:varnish:4.0.2:rc-1:*:*:*:*:*:*
varnish-cache varnish 4.0.3 cpe:2.3:a:varnish-cache:varnish:4.0.3:rc-1:*:*:*:*:*:*
varnish-cache varnish 4.0.3 cpe:2.3:a:varnish-cache:varnish:4.0.3:rc-2:*:*:*:*:*:*
varnish-cache varnish 4.0.3 cpe:2.3:a:varnish-cache:varnish:4.0.3:rc-2-proper:*:*:*:*:*:*
varnish-cache varnish 4.0.3 cpe:2.3:a:varnish-cache:varnish:4.0.3:rc-3:*:*:*:*:*:*
varnish_cache_project varnish_cache 4.0.1 cpe:2.3:a:varnish_cache_project:varnish_cache:4.0.1:*:*:*:*:*:*:*
varnish_cache_project varnish_cache 4.0.2 cpe:2.3:a:varnish_cache_project:varnish_cache:4.0.2:*:*:*:*:*:*:*
varnish_cache_project varnish_cache 4.0.3 cpe:2.3:a:varnish_cache_project:varnish_cache:4.0.3:*:*:*:*:*:*:*
varnish_cache_project varnish_cache 4.0.4 cpe:2.3:a:varnish_cache_project:varnish_cache:4.0.4:*:*:*:*:*:*:*
varnish-cache varnish 4.1.0 cpe:2.3:a:varnish-cache:varnish:4.1.0:*:*:*:*:*:*:*
varnish-software varnish_cache 4.1.0 cpe:2.3:a:varnish-software:varnish_cache:4.1.0:beta1:*:*:*:*:*:*
varnish-software varnish_cache 4.1.0 cpe:2.3:a:varnish-software:varnish_cache:4.1.0:technology_preview1:*:*:*:*:*:*
varnish-software varnish_cache 4.1.1 cpe:2.3:a:varnish-software:varnish_cache:4.1.1:*:*:*:*:*:*:*
varnish-software varnish_cache 4.1.1 cpe:2.3:a:varnish-software:varnish_cache:4.1.1:beta1:*:*:*:*:*:*
varnish-software varnish_cache 4.1.1 cpe:2.3:a:varnish-software:varnish_cache:4.1.1:beta2:*:*:*:*:*:*
varnish-software varnish_cache 4.1.2 cpe:2.3:a:varnish-software:varnish_cache:4.1.2:*:*:*:*:*:*:*
varnish-software varnish_cache 4.1.2 cpe:2.3:a:varnish-software:varnish_cache:4.1.2:beta1:*:*:*:*:*:*
varnish-software varnish_cache 4.1.2 cpe:2.3:a:varnish-software:varnish_cache:4.1.2:beta2:*:*:*:*:*:*
varnish-software varnish_cache 4.1.3 cpe:2.3:a:varnish-software:varnish_cache:4.1.3:*:*:*:*:*:*:*
varnish-software varnish_cache 4.1.3 cpe:2.3:a:varnish-software:varnish_cache:4.1.3:beta1:*:*:*:*:*:*
varnish-software varnish_cache 4.1.3 cpe:2.3:a:varnish-software:varnish_cache:4.1.3:beta2:*:*:*:*:*:*
varnish-software varnish_cache 4.1.4 cpe:2.3:a:varnish-software:varnish_cache:4.1.4:*:*:*:*:*:*:*
varnish-software varnish_cache 4.1.4 cpe:2.3:a:varnish-software:varnish_cache:4.1.4:beta1:*:*:*:*:*:*
varnish-software varnish_cache 4.1.4 cpe:2.3:a:varnish-software:varnish_cache:4.1.4:beta2:*:*:*:*:*:*
varnish-software varnish_cache 4.1.4 cpe:2.3:a:varnish-software:varnish_cache:4.1.4:beta3:*:*:*:*:*:*
varnish-software varnish_cache 4.1.5 cpe:2.3:a:varnish-software:varnish_cache:4.1.5:*:*:*:*:*:*:*
varnish-software varnish_cache 4.1.5 cpe:2.3:a:varnish-software:varnish_cache:4.1.5:beta1:*:*:*:*:*:*
varnish-software varnish_cache 4.1.5 cpe:2.3:a:varnish-software:varnish_cache:4.1.5:beta2:*:*:*:*:*:*
varnish-software varnish_cache 4.1.6 cpe:2.3:a:varnish-software:varnish_cache:4.1.6:*:*:*:*:*:*:*
varnish-software varnish_cache 4.1.7 cpe:2.3:a:varnish-software:varnish_cache:4.1.7:*:*:*:*:*:*:*
varnish_cache_project varnish_cache 5.0.0 cpe:2.3:a:varnish_cache_project:varnish_cache:5.0.0:*:*:*:*:*:*:*
varnish_cache_project varnish_cache 5.1.0 cpe:2.3:a:varnish_cache_project:varnish_cache:5.1.0:*:*:*:*:*:*:*
varnish_cache_project varnish_cache 5.1.1 cpe:2.3:a:varnish_cache_project:varnish_cache:5.1.1:*:*:*:*:*:*:*
varnish_cache_project varnish_cache 5.1.2 cpe:2.3:a:varnish_cache_project:varnish_cache:5.1.2:*:*:*:*:*:*:*

References for CVE-2017-12425

cvelogic Threat Intelligence