First published: Mon May 09 2016(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/squid | <3.5.18 | 3.5.18 |
Oracle Linux | =6 | |
Oracle Linux | =7 | |
Squid Web Proxy Cache | <=3.5.17 | |
Ubuntu | =12.04 | |
Ubuntu | =14.04 | |
Ubuntu | =15.10 | |
Ubuntu | =16.04 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-4554 has a medium severity level due to its potential for abuse via header smuggling and cache poisoning.
To fix CVE-2016-4554, upgrade Squid to version 3.5.18 or later.
CVE-2016-4554 affects Squid versions up to and including 3.5.17.
Yes, CVE-2016-4554 can be exploited remotely by an attacker through a crafted HTTP Host header.
CVE-2016-4554 can allow attackers to conduct cache poisoning attacks, compromising the integrity of the cache data.