7.5
CWE
20
Advisory Published
Updated

CVE-2016-2571: Input Validation

First published: Sat Feb 27 2016(Updated: )

http.cc in Squid 3.x before 3.5.15 and 4.x before 4.0.7 proceeds with the storage of certain data after a response-parsing failure, which allows remote HTTP servers to cause a denial of service (assertion failure and daemon exit) via a malformed response.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
Squid Web Proxy Cache=3.0
Squid Web Proxy Cache=3.0
Squid Web Proxy Cache=3.0
Squid Web Proxy Cache=3.0
Squid Web Proxy Cache=3.0
Squid Web Proxy Cache=3.0
Squid Web Proxy Cache=3.0
Squid Web Proxy Cache=3.0
Squid Web Proxy Cache=3.0-rc4
Squid Web Proxy Cache=3.0.stable1
Squid Web Proxy Cache=3.0.stable2
Squid Web Proxy Cache=3.0.stable3
Squid Web Proxy Cache=3.0.stable4
Squid Web Proxy Cache=3.0.stable5
Squid Web Proxy Cache=3.0.stable6
Squid Web Proxy Cache=3.0.stable7
Squid Web Proxy Cache=3.0.stable8
Squid Web Proxy Cache=3.0.stable9
Squid Web Proxy Cache=3.0.stable10
Squid Web Proxy Cache=3.0.stable11
Squid Web Proxy Cache=3.0.stable11-rc1
Squid Web Proxy Cache=3.0.stable12
Squid Web Proxy Cache=3.0.stable13
Squid Web Proxy Cache=3.0.stable14
Squid Web Proxy Cache=3.0.stable15
Squid Web Proxy Cache=3.0.stable16
Squid Web Proxy Cache=3.0.stable16-rc1
Squid Web Proxy Cache=3.0.stable17
Squid Web Proxy Cache=3.0.stable18
Squid Web Proxy Cache=3.0.stable19
Squid Web Proxy Cache=3.0.stable20
Squid Web Proxy Cache=3.0.stable21
Squid Web Proxy Cache=3.0.stable22
Squid Web Proxy Cache=3.0.stable23
Squid Web Proxy Cache=3.0.stable24
Squid Web Proxy Cache=3.0.stable25
Squid Web Proxy Cache=3.1
Squid Web Proxy Cache=3.1.0.1
Squid Web Proxy Cache=3.1.0.2
Squid Web Proxy Cache=3.1.0.3
Squid Web Proxy Cache=3.1.0.4
Squid Web Proxy Cache=3.1.0.5
Squid Web Proxy Cache=3.1.0.6
Squid Web Proxy Cache=3.1.0.7
Squid Web Proxy Cache=3.1.0.8
Squid Web Proxy Cache=3.1.0.9
Squid Web Proxy Cache=3.1.0.10
Squid Web Proxy Cache=3.1.0.11
Squid Web Proxy Cache=3.1.0.12
Squid Web Proxy Cache=3.1.0.13
Squid Web Proxy Cache=3.1.0.14
Squid Web Proxy Cache=3.1.0.15
Squid Web Proxy Cache=3.1.0.16
Squid Web Proxy Cache=3.1.0.17
Squid Web Proxy Cache=3.1.0.18
Squid Web Proxy Cache=3.1.1
Squid Web Proxy Cache=3.1.2
Squid Web Proxy Cache=3.1.3
Squid Web Proxy Cache=3.1.4
Squid Web Proxy Cache=3.1.5
Squid Web Proxy Cache=3.1.5.1
Squid Web Proxy Cache=3.1.6
Squid Web Proxy Cache=3.1.7
Squid Web Proxy Cache=3.1.8
Squid Web Proxy Cache=3.1.9
Squid Web Proxy Cache=3.1.10
Squid Web Proxy Cache=3.1.11
Squid Web Proxy Cache=3.1.12
Squid Web Proxy Cache=3.1.13
Squid Web Proxy Cache=3.1.14
Squid Web Proxy Cache=3.1.15
Squid Web Proxy Cache=3.2.0.1
Squid Web Proxy Cache=3.2.0.2
Squid Web Proxy Cache=3.2.0.3
Squid Web Proxy Cache=3.2.0.4
Squid Web Proxy Cache=3.2.0.5
Squid Web Proxy Cache=3.2.0.6
Squid Web Proxy Cache=3.2.0.7
Squid Web Proxy Cache=3.2.0.8
Squid Web Proxy Cache=3.2.0.9
Squid Web Proxy Cache=3.2.0.10
Squid Web Proxy Cache=3.2.0.11
Squid Web Proxy Cache=3.2.0.12
Squid Web Proxy Cache=3.2.0.13
Squid Web Proxy Cache=3.2.0.14
Squid Web Proxy Cache=3.2.0.15
Squid Web Proxy Cache=3.2.0.16
Squid Web Proxy Cache=3.2.0.17
Squid Web Proxy Cache=3.2.0.18
Squid Web Proxy Cache=3.2.0.19
Squid Web Proxy Cache=3.2.1
Squid Web Proxy Cache=3.2.2
Squid Web Proxy Cache=3.2.3
Squid Web Proxy Cache=3.2.4
Squid Web Proxy Cache=3.2.5
Squid Web Proxy Cache=3.2.6
Squid Web Proxy Cache=3.2.7
Squid Web Proxy Cache=3.2.8
Squid Web Proxy Cache=3.2.9
Squid Web Proxy Cache=3.2.10
Squid Web Proxy Cache=3.2.11
Squid Web Proxy Cache=3.2.12
Squid Web Proxy Cache=3.2.13
Squid Web Proxy Cache=3.3.0
Squid Web Proxy Cache=3.3.0.2
Squid Web Proxy Cache=3.3.0.3
Squid Web Proxy Cache=3.3.1
Squid Web Proxy Cache=3.3.2
Squid Web Proxy Cache=3.3.3
Squid Web Proxy Cache=3.3.4
Squid Web Proxy Cache=3.3.5
Squid Web Proxy Cache=3.3.6
Squid Web Proxy Cache=3.3.7
Squid Web Proxy Cache=3.3.8
Squid Web Proxy Cache=3.3.9
Squid Web Proxy Cache=3.3.10
Squid Web Proxy Cache=3.3.11
Squid Web Proxy Cache=3.3.12
Squid Web Proxy Cache=3.3.13
Squid Web Proxy Cache=3.4.0.1
Squid Web Proxy Cache=3.4.0.2
Squid Web Proxy Cache=3.4.0.3
Squid Web Proxy Cache=3.4.1
Squid Web Proxy Cache=3.4.2
Squid Web Proxy Cache=3.4.3
Squid Web Proxy Cache=3.4.4
Squid Web Proxy Cache=3.4.8
Squid Web Proxy Cache=3.4.9
Squid Web Proxy Cache=3.4.10
Squid Web Proxy Cache=3.4.11
Squid Web Proxy Cache=3.4.12
Squid Web Proxy Cache=3.4.13
Squid Web Proxy Cache=3.5.0.1
Squid Web Proxy Cache=3.5.0.2
Squid Web Proxy Cache=3.5.0.3
Squid Web Proxy Cache=3.5.0.4
Squid Web Proxy Cache=3.5.1
Squid Web Proxy Cache=4.0.1
Squid Web Proxy Cache=4.0.2
Squid Web Proxy Cache=4.0.3
Squid Web Proxy Cache=4.0.4
Squid Web Proxy Cache=4.0.5
Squid Web Proxy Cache=4.0.6
debian/squid
4.13-10+deb11u3
4.13-10+deb11u4
5.7-2+deb12u2
6.13-1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2016-2571?

    CVE-2016-2571 is considered a high severity vulnerability due to its potential to cause denial of service.

  • How do I fix CVE-2016-2571?

    To fix CVE-2016-2571, upgrade to Squid version 3.5.15 or later, or 4.0.7 or later.

  • What causes the CVE-2016-2571 vulnerability?

    CVE-2016-2571 is caused by the mishandling of malformed HTTP responses in certain Squid versions.

  • Is CVE-2016-2571 easy to exploit?

    Yes, CVE-2016-2571 can be exploited easily by sending specially crafted HTTP responses.

  • Does CVE-2016-2571 affect all versions of Squid?

    CVE-2016-2571 affects Squid versions prior to 3.5.15 and 4.0.7.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203