CVE-2015-3455

Priority
Description
Squid 3.2.x before 3.2.14, 3.3.x before 3.3.14, 3.4.x before 3.4.13, and
3.5.x before 3.5.4, when configured with client-first SSL-bump, do not
properly validate the domain or hostname fields of X.509 certificates,
which allows man-in-the-middle attackers to spoof SSL servers via a valid
certificate.
Assigned-to
mdeslaur
Notes
mdeslauronly an issue if squid3 is built with --enable-ssl, which isn't
the case on debian/ubuntu for licensing reasons.
However, we should probably fix this anyway as rebuilding
the Ubuntu package locally to enable ssl is a common scenario.
3.1.x not affected
Package
Upstream:released (3.5.4,3.4.13,3.3.14,3.2.14)
Ubuntu 14.04 ESM (Trusty Tahr):DNE (trusty was released [3.3.8-1ubuntu6.6])
Ubuntu 16.04 LTS (Xenial Xerus):released (3.5.12-1ubuntu6)
Patches:
Upstream:http://www.squid-cache.org/Versions/v3/3.3/changesets/squid-3.3-12690.patch (3.3)
More Information

Updated: 2020-01-29 19:52:09 UTC (commit 768ceb2fdee6790d707d0f681e1b54916744af1e)