CVE-2016-4554

Description

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.

Category

8.6
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 62.49% Top 5%
Vendor Advisory gentoo.org Vendor Advisory opensuse.org Vendor Advisory ubuntu.com Vendor Advisory redhat.com Vendor Advisory opensuse.org Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory opensuse.org Vendor Advisory debian.org Vendor Advisory squid-cache.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://security.gentoo.org/glsa/201607-01 vendor advisory
http://www.oracle.com/technetwork/topics/security/linuxbulletinapr2016-2952096.html third party advisory
http://www.squid-cache.org/Versions/v3/3.3/changesets/SQUID-2016_8.patch patch
http://www.squid-cache.org/Versions/v3/3.4/changesets/SQUID-2016_8.patch patch
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00010.html vendor advisory
http://www.squid-cache.org/Versions/v3/3.1/changesets/SQUID-2016_8.patch patch
http://www.ubuntu.com/usn/USN-2995-1 third party advisory vendor advisory
http://www.securitytracker.com/id/1035769 third party advisory vdb entry
http://www.squid-cache.org/Versions/v3/3.2/changesets/SQUID-2016_8.patch patch
https://access.redhat.com/errata/RHSA-2016:1140 vendor advisory
http://lists.opensuse.org/opensuse-updates/2016-08/msg00069.html vendor advisory
https://access.redhat.com/errata/RHSA-2016:1138 vendor advisory
https://access.redhat.com/errata/RHSA-2016:1139 vendor advisory
http://www.squid-cache.org/Advisories/SQUID-2016_8.txt vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2016-08/msg00040.html vendor advisory
http://www.squid-cache.org/Versions/v3/3.5/changesets/SQUID-2016_8.patch patch
http://www.debian.org/security/2016/dsa-3625 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2016-4554?
CVE-2016-4554 has been scored as a high severity vulnerability.
How to fix CVE-2016-4554?
To fix CVE-2016-4554, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2016-4554 being actively exploited in the wild?
It is possible that CVE-2016-4554 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~62% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.