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.
{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "squid",
"binary_version": "3.3.8-1ubuntu6.8"
},
{
"binary_name": "squid-cgi",
"binary_version": "3.3.8-1ubuntu6.8"
},
{
"binary_name": "squid-purge",
"binary_version": "3.3.8-1ubuntu6.8"
},
{
"binary_name": "squid3",
"binary_version": "3.3.8-1ubuntu6.8"
},
{
"binary_name": "squid3-common",
"binary_version": "3.3.8-1ubuntu6.8"
},
{
"binary_name": "squidclient",
"binary_version": "3.3.8-1ubuntu6.8"
}
]
}
{
"availability": "No subscription required",
"binaries": [
{
"binary_name": "squid",
"binary_version": "3.5.12-1ubuntu7.2"
},
{
"binary_name": "squid-cgi",
"binary_version": "3.5.12-1ubuntu7.2"
},
{
"binary_name": "squid-common",
"binary_version": "3.5.12-1ubuntu7.2"
},
{
"binary_name": "squid-purge",
"binary_version": "3.5.12-1ubuntu7.2"
},
{
"binary_name": "squid3",
"binary_version": "3.5.12-1ubuntu7.2"
},
{
"binary_name": "squidclient",
"binary_version": "3.5.12-1ubuntu7.2"
}
]
}