Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2017-8807: 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.

65
This week
CRITICAL 9.1REMOTEWATCHLISTUPGRADEUPGRADEMITIGATE

CVE-2017-8807 is a critical-severity flaw (CVSS 9.1) affecting varnish, varnish cache, debian linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.1 allows remote attackers to obtain sensitive information from process memory because a VFP_GetStorage buffer is larger than intended in certain circumstances involving -sfile Stevedore transient objects.

Why this priority

  • Critical severity
  • EPSS top 9%: very likely to be exploited
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score9.1 (Critical)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance4.1% (top 9%)
CISA exploited listNo
WeaknessCWE-119
Published2017-11-16
Last modified2026-06-17
Publisher (CNA): Debian GNU/Linux · Vendor: debian · varnish cache project · varnish-cache

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

varnish-cache varnish UPGRADE
Affected: >= 4.1.0 and < 4.1.9
Fixed in: 4.1.9
Safe to downgrade to: a release before 4.1.0
1. Check installed version
apt-cache policy varnish || rpm -q varnish || varnish --version
2. UPGRADE to 4.1.9 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade varnish
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade varnish
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.1.0 (Debian / Ubuntu)
apt-cache madison varnish sudo apt install varnish=<VERSION_BEFORE_4.1.0> sudo apt-mark hold varnish
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list varnish sudo dnf downgrade varnish-<VERSION_BEFORE_4.1.0> sudo dnf versionlock add varnish
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
varnish cache project varnish cache UPGRADE
Affected: >= 5.0.0 and < 5.2.1
Fixed in: 5.2.1
Safe to downgrade to: a release before 5.0.0
1. Check installed version
apt-cache policy varnish-cache || rpm -q varnish-cache || varnish-cache --version
2. UPGRADE to 5.2.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade varnish-cache
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade varnish-cache
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 5.0.0 (Debian / Ubuntu)
apt-cache madison varnish-cache sudo apt install varnish-cache=<VERSION_BEFORE_5.0.0> sudo apt-mark hold varnish-cache
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list varnish-cache sudo dnf downgrade varnish-cache-<VERSION_BEFORE_5.0.0> sudo dnf versionlock add varnish-cache
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
debian debian linux MITIGATE
Affected: 9.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 9.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-8807?

varnish: upgrade to 4.1.9; varnish cache: upgrade to 5.2.1; debian linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-8807 being exploited?

CVE-2017-8807 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-8807 affect?

CVE-2017-8807 affects varnish, varnish cache, debian linux. Severity is critical (CVSS 9.1). 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.1 allows remote attackers to obtain sensitive information from process memory because a VFP_GetStorage buffer is larger than inten

How urgent is CVE-2017-8807?

Priority 65/100. Critical severity; EPSS top 9%: very likely to be exploited; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Debian vulnerabilities · Varnish vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.