mime_header.cc in Squid before 3.5.18 allows remote attackers to bypass intended same-origin restrictions and possibly conduct cache-poisoning attacks via a crafted HTTP Host header, aka a “header smuggling” issue.
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/1035769
www.squid-cache.org/Advisories/SQUID-2016_8.txt
www.squid-cache.org/Versions/v3/3.1/changesets/SQUID-2016_8.patch
www.squid-cache.org/Versions/v3/3.2/changesets/SQUID-2016_8.patch
www.squid-cache.org/Versions/v3/3.3/changesets/SQUID-2016_8.patch
www.squid-cache.org/Versions/v3/3.4/changesets/SQUID-2016_8.patch
www.squid-cache.org/Versions/v3/3.5/changesets/SQUID-2016_8.patch
www.ubuntu.com/usn/USN-2995-1
access.redhat.com/errata/RHSA-2016:1138
access.redhat.com/errata/RHSA-2016:1139
access.redhat.com/errata/RHSA-2016:1140
security.gentoo.org/glsa/201607-01