The proxy contains a String object class with 64KB content limits. Some code paths do not bounds check before appending to these String and overflow leads to an assertion which terminates all client transactions using the proxy, including those unrelated to the limit being exceeded. Upstream patches: http://www.squid-cache.org/Versions/v3/3.5/changesets/squid-3.5-13991.patch http://www.squid-cache.org/Versions/v4/changesets/squid-4-14552.patch External references: http://www.squid-cache.org/Advisories/SQUID-2016_2.txt CVE assignment: http://seclists.org/oss-sec/2016/q1/442
Added CVE 2016-2570, as it relates to other patches for the same issue. Upstream comment about this: This patch fixes the other related variant of the basic problem. Though this instance is not triggerable from outside a controlled CDN environment Upstream patches for this CVE: http://www.squid-cache.org/Versions/v3/3.5/changesets/squid-3.5-13993.patch http://www.squid-cache.org/Versions/v4/changesets/squid-4-14549.patch
*** Bug 1311584 has been marked as a duplicate of this bug. ***
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2016:2600 https://rhn.redhat.com/errata/RHSA-2016-2600.html
Statement: Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.