CVE-2016-4553: client_side.cc in Squid before 3.5.18 and 4.x before 4.0.10 does not properly ignore the Host header when absolute-URI is provided, which…
Noroxi assessment
Priority: Plan (action score 58/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 79.9% (FIRST EPSS); higher than 99.6% of all records.
- 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.
- Fixed version: squid3 (Debian:8) 3.4.8-6+deb8u3; squid (openSUSE:Tumbleweed) 4.16-1.5; squid34 (Red Hat:enterprise_linux:6::server) 7:3.4.14-9.el6_8.3.
Add it to your regular patch cycle. Upgrade to squid3 (Debian:8) 3.4.8-6+deb8u3; squid (openSUSE:Tumbleweed) 4.16-1.5; squid34 (Red Hat:enterprise_linux:6::server) 7:3.4.14-9.el6_8.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
client_side.cc in Squid before 3.5.18 and 4.x before 4.0.10 does not properly ignore the Host header when absolute-URI is provided, which allows remote attackers to conduct cache-poisoning attacks via an HTTP request.
- Published
- May 10, 2016
- Updated
- Jun 16, 2026
- EPSS
- 79.9% · 99th percentile
- CWE
- CWE-345
Report tools
Action score
58
Add it to your regular patch cycle.
- CVSS
- 34 / 40 · 8.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 24 / 30 · 79.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| squid-cache | squid | cpe:2.3:a:squid-cache:squid |
| oracle | linux | cpe:2.3:o:oracle:linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux12.04
- canonical ubuntu linux14.04
- canonical ubuntu linux15.10
- canonical ubuntu linux16.04
- oracle linux7
- squid-cache squidup to 3.5.17 inclusive
- squid-cache squid4.0.1
- squid-cache squid4.0.2
+7 more rows
- squid-cache squid4.0.3
- squid-cache squid4.0.4
- squid-cache squid4.0.5
- squid-cache squid4.0.6
- squid-cache squid4.0.7
- squid-cache squid4.0.8
- squid-cache squid4.0.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:8 | squid3 | before 3.4.8-6+deb8u3 | 3.4.8-6+deb8u3 |
| openSUSE:Tumbleweed | squid | before 4.16-1.5 | 4.16-1.5 |
| Red Hat:enterprise_linux:6::server | squid34 | before 7:3.4.14-9.el6_8.3 | 7:3.4.14-9.el6_8.3 |
| Red Hat:enterprise_linux:6::server | squid34-debuginfo | before 7:3.4.14-9.el6_8.3 | 7:3.4.14-9.el6_8.3 |
| Red Hat:enterprise_linux:7::server | squid | before 7:3.3.8-26.el7_2.3 | 7:3.3.8-26.el7_2.3 |
| Red Hat:enterprise_linux:7::server | squid-debuginfo | before 7:3.3.8-26.el7_2.3 | 7:3.3.8-26.el7_2.3 |
| Red Hat:enterprise_linux:7::server | squid-sysvinit | before 7:3.3.8-26.el7_2.3 | 7:3.3.8-26.el7_2.3 |
| SUSE:Linux Enterprise Server 12 SP1 | squid | before 3.3.14-20.2 | 3.3.14-20.2 |
Same product
canonical: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-3493The overlayfs implementation in the linux kernel did not properly validate with respect to user namespaces the setting of file capabilities…KEV76This week
- CVE-2017-14492Heap-based buffer overflow in dnsmasq before 2.78 allows remote attackers to cause a denial of service (crash) or execute arbitrary code…67This week
- CVE-2017-14493Stack-based buffer overflow in dnsmasq before 2.78 allows remote attackers to cause a denial of service (crash) or execute arbitrary code…65This week
Published before and after this one in the same product
- ← EarlierCVE-2016-4052Apr 25, 2016 · Multiple stack-based buffer overflows in Squid 3.x before 3.5.17 and 4.x before 4.0.9 allow remote HTTP servers to cause a denial of…36Monitor
- ← EarlierCVE-2016-4054Apr 25, 2016 · Buffer overflow in Squid 3.x before 3.5.17 and 4.x before 4.0.9 allows remote attackers to execute arbitrary code via crafted Edge Side…55Plan
- Later →CVE-2016-1578May 13, 2016 · Use-after-free vulnerability in Oxide allows remote attackers to cause a denial of service (application crash) or execute arbitrary code…40Plan
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 |
|---|---|---|
| debian:squid3 | 3.4.8-6+deb8u3 · Debian:8 | Package registry (OSV) |
| opensuse:squid | 4.16-1.5 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:squid | 7:3.3.8-26.el7_2.3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:squid-debuginfo | 7:3.3.8-26.el7_2.3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:squid-sysvinit | 7:3.3.8-26.el7_2.3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:squid34 | 7:3.4.14-9.el6_8.3 · Red Hat:enterprise_linux:6::server | Package registry (OSV) |
| red hat:squid34-debuginfo | 7:3.4.14-9.el6_8.3 · Red Hat:enterprise_linux:6::server | Package registry (OSV) |
| suse:squid | 3.3.14-20.2 · SUSE:Linux Enterprise Server 12 SP1 | 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.
Not on record for this CVE: researcher credit · variant or chain candidate · public bounty program.
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
- high · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-345 · Insufficient Verification of Data AuthenticityCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
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)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Content SpoofingCAPEC-148likelihood: Medium · Medium
- Spoofing of UDDI/ebXML MessagesCAPEC-218Medium
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (12 more)Show less
- lists.opensuse.org/opensuse-security-announce/2016-08/msg00010.html
- lists.opensuse.org/opensuse-security-announce/2016-08/msg00040.html
- lists.opensuse.org/opensuse-updates/2016-08/msg00069.html
- www.debian.org/security/2016/dsa-3625
- www.oracle.com/technetwork/topics/security/linuxbulletinapr2016-2952096.html
- www.securitytracker.com/id/1035768
- www.squid-cache.org/Advisories/SQUID-2016_7.txt
- www.squid-cache.org/Versions/v3/3.5/changesets/squid-3.5-14039.patch
- www.ubuntu.com/usn/USN-2995-1
- access.redhat.com/errata/RHSA-2016:1139
- access.redhat.com/errata/RHSA-2016:1140
- security.gentoo.org/glsa/201607-01
Vendor advisories and official records. Exploit/PoC links are deliberately left out.