kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Document three security advisories for the squid and squid-devel

Browse source 
ports.  CVE numbers are not yet available.

PR:		209334
Submitted by:	timp87@gmail.com (maintainer)
This commit is contained in:
Matthew Seaman 2016-05-07 11:56:27 +00:00
parent 8e7ac9bef6
commit 37549c4c9b
Notes: svn2git 2021-03-31 03:12:20 +00:00 
svn path=/head/; revision=414774
1 changed files with 76 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

76
security/vuxml/vuln.xml
View file

@ -58,6 +58,82 @@ Notes:
* Do not forget port variants (linux-f10-libxml2, libxml2, etc.)
-->
<vuxml xmlns="http://www.vuxml.org/apps/vuxml-1">
<vuln vid="25e5205b-1447-11e6-9ead-6805ca0b3d42">
<topic>squid -- multiple vulnerabilities</topic>
<affects>
<package>
<name>squid</name>
<range><ge>3.0.0</ge><lt>3.5.18</lt></range>
</package>
<package>
<name>squid-devel</name>
<range><ge>4.0.0</ge><lt>4.0.10</lt></range>
</package>
</affects>
<description>
<body xmlns="http://www.w3.org/1999/xhtml">
<p>The squid development team reports:</p>
<blockquote cite="http://www.squid-cache.org/Advisories/SQUID-2016_7.txt">
<dl>
<dt>Problem Description:</dt>
<dd>Due to incorrect data validation of intercepted HTTP
Request messages Squid is vulnerable to clients bypassing
the protection against CVE-2009-0801 related issues. This
leads to cache poisoning.</dd>
<dt>Severity:</dt>
<dd>This problem is serious because it allows any client,
including browser scripts, to bypass local security and
poison the proxy cache and any downstream caches with
content from an arbitrary source.</dd>
</dl>
</blockquote>
<blockquote cite="http://www.squid-cache.org/Advisories/SQUID-2016_8.txt">
<dl>
<dt>Problem Description:</dt>
<dd>Due to incorrect input validation Squid is vulnerable
to a header smuggling attack leading to cache poisoning
and to bypass of same-origin security policy in Squid and
some client browsers.</dd>
<dt>Severity:</dt>
<dd>This problem allows a client to smuggle Host header
value past same-origin security protections to cause Squid
operating as interception or reverse-proxy to contact the
wrong origin server. Also poisoning any downstream cache
which stores the response.</dd>
<dd>However, the cache poisoning is only possible if the
caching agent (browser or explicit/forward proxy) is not
following RFC 7230 processing guidelines and lets the
smuggled value through.</dd>
</dl>
</blockquote>
<blockquote cite="http://www.squid-cache.org/Advisories/SQUID-2016_9.txt">
<dl>
<dt>Problem Description:</dt>
<dd>Due to incorrect pointer handling and reference
counting Squid is vulnerable to a denial of service attack
when processing ESI responses.</dd>
<dt>Severity:</dt>
<dd>These problems allow a remote server delivering
certain ESI response syntax to trigger a denial of service
for all clients accessing the Squid service.</dd>
<dd>Due to unrelated changes Squid-3.5 has become
vulnerable to some regular ESI server responses also
triggering one or more of these issues.</dd>
</dl>
</blockquote>
</body>
</description>
<references>
<url>http://www.squid-cache.org/Advisories/SQUID-2016_7.txt</url>
<url>http://www.squid-cache.org/Advisories/SQUID-2016_8.txt</url>
<url>http://www.squid-cache.org/Advisories/SQUID-2016_9.txt</url>
</references>
<dates>
<discovery>2016-05-06</discovery>
<entry>2016-05-07</entry>
</dates>
</vuln>
<vuln vid="0d724b05-687f-4527-9c03-af34d3b094ec">
<topic>ImageMagick -- multiple vulnerabilities</topic>
<affects>