CVE-2016-4051: Buffer Overflow

Published Apr 21, 2016
·
Updated

Buffer overflow in cachemgr.cgi in Squid 2.x, 3.x before 3.5.17, and 4.x before 4.0.9 might allow remote attackers to cause a denial of service or execute arbitrary code by seeding manager reports with crafted data.

Other sources

Due to incorrect buffer management Squid cachemgr.cgi tool is vulnerable to a buffer overflow when processing remotely supplied inputs relayed to it from Squid.

External references:

http://www.squid-cache.org/Advisories/SQUID-20165.txt

Upstream fixes:

[RHEL-7] www.squid-cache.org/Versions/v3/3.3/changesets/SQUID-20165.patch

[Fedora-23] http://www.squid-cache.org/Versions/v3/3.5/changesets/SQUID-20165.patch

[Fedora-22] http://www.squid-cache.org/Versions/v3/3.4/changesets/SQUID-20165.patch

Red Hat

Affected Software

156 affected componentsFixes available
redhat/squid<3.5.17
3.5.17
redhat/squid<4.0.9
4.0.9
Canonical Ubuntu Linux=12.04
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=15.10
Canonical Ubuntu Linux=16.04
Oracle Linux=6
Oracle Linux=7
Squid-Cache Squid=2.0
Squid-Cache Squid=2.1
Squid-Cache Squid=2.2
Squid-Cache Squid=2.3
Squid-Cache Squid=2.4
Squid-Cache Squid=2.5
Squid-Cache Squid=2.6
Squid-Cache Squid=2.7
Squid-Cache Squid=3.0
Squid-Cache Squid=3.1
Squid-Cache Squid=3.1.0.1
Squid-Cache Squid=3.1.0.2
Squid-Cache Squid=3.1.0.3
Squid-Cache Squid=3.1.0.4
Squid-Cache Squid=3.1.0.5
Squid-Cache Squid=3.1.0.6
Squid-Cache Squid=3.1.0.7
Squid-Cache Squid=3.1.0.8
Squid-Cache Squid=3.1.0.9
Squid-Cache Squid=3.1.0.10
Squid-Cache Squid=3.1.0.11
Squid-Cache Squid=3.1.0.12
Squid-Cache Squid=3.1.0.13
Squid-Cache Squid=3.1.0.14
Squid-Cache Squid=3.1.0.15
Squid-Cache Squid=3.1.0.16
Squid-Cache Squid=3.1.0.17
Squid-Cache Squid=3.1.0.18
Squid-Cache Squid=3.1.1
Squid-Cache Squid=3.1.2
Squid-Cache Squid=3.1.3
Squid-Cache Squid=3.1.4
Squid-Cache Squid=3.1.5
Squid-Cache Squid=3.1.5.1
Squid-Cache Squid=3.1.6
Squid-Cache Squid=3.1.7
Squid-Cache Squid=3.1.8
Squid-Cache Squid=3.1.9
Squid-Cache Squid=3.1.10
Squid-Cache Squid=3.1.11
Squid-Cache Squid=3.1.12
Squid-Cache Squid=3.1.12.1
Squid-Cache Squid=3.1.12.2
Squid-Cache Squid=3.1.12.3
Squid-Cache Squid=3.1.13
Squid-Cache Squid=3.1.14
Squid-Cache Squid=3.1.15
Squid-Cache Squid=3.1.16
Squid-Cache Squid=3.1.17
Squid-Cache Squid=3.1.18
Squid-Cache Squid=3.1.19
Squid-Cache Squid=3.1.20
Squid-Cache Squid=3.1.21
Squid-Cache Squid=3.1.22
Squid-Cache Squid=3.2.0.1
Squid-Cache Squid=3.2.0.2
Squid-Cache Squid=3.2.0.3
Squid-Cache Squid=3.2.0.4
Squid-Cache Squid=3.2.0.5
Squid-Cache Squid=3.2.0.6
Squid-Cache Squid=3.2.0.7
Squid-Cache Squid=3.2.0.8
Squid-Cache Squid=3.2.0.9
Squid-Cache Squid=3.2.0.10
Squid-Cache Squid=3.2.0.11
Squid-Cache Squid=3.2.0.12
Squid-Cache Squid=3.2.0.13
Squid-Cache Squid=3.2.0.14
Squid-Cache Squid=3.2.0.15
Squid-Cache Squid=3.2.0.16
Squid-Cache Squid=3.2.0.17
Squid-Cache Squid=3.2.0.18
Squid-Cache Squid=3.2.0.19
Squid-Cache Squid=3.2.1
Squid-Cache Squid=3.2.2
Squid-Cache Squid=3.2.3
Squid-Cache Squid=3.2.4
Squid-Cache Squid=3.2.5
Squid-Cache Squid=3.2.6
Squid-Cache Squid=3.2.7
Squid-Cache Squid=3.2.8
Squid-Cache Squid=3.2.9
Squid-Cache Squid=3.2.10
Squid-Cache Squid=3.2.11
Squid-Cache Squid=3.2.12
Squid-Cache Squid=3.2.13
Squid-Cache Squid=3.3.0
Squid-Cache Squid=3.3.0.1
Squid-Cache Squid=3.3.0.2
Squid-Cache Squid=3.3.0.3
Squid-Cache Squid=3.3.1
Squid-Cache Squid=3.3.2
Squid-Cache Squid=3.3.3
Squid-Cache Squid=3.3.4
Squid-Cache Squid=3.3.5
Squid-Cache Squid=3.3.6
Squid-Cache Squid=3.3.7
Squid-Cache Squid=3.3.8
Squid-Cache Squid=3.3.9
Squid-Cache Squid=3.3.10
Squid-Cache Squid=3.3.11
Squid-Cache Squid=3.3.12
Squid-Cache Squid=3.3.13
Squid-Cache Squid=3.3.14
Squid-Cache Squid=3.4.0.1
Squid-Cache Squid=3.4.0.2
Squid-Cache Squid=3.4.0.3
Squid-Cache Squid=3.4.1
Squid-Cache Squid=3.4.2
Squid-Cache Squid=3.4.3
Squid-Cache Squid=3.4.4
Squid-Cache Squid=3.4.4.1
Squid-Cache Squid=3.4.4.2
Squid-Cache Squid=3.4.8
Squid-Cache Squid=3.4.9
Squid-Cache Squid=3.4.10
Squid-Cache Squid=3.4.11
Squid-Cache Squid=3.4.12
Squid-Cache Squid=3.4.13
Squid-Cache Squid=3.4.14
Squid-Cache Squid=3.5.0.1
Squid-Cache Squid=3.5.0.2
Squid-Cache Squid=3.5.0.3
Squid-Cache Squid=3.5.0.4
Squid-Cache Squid=3.5.1
Squid-Cache Squid=3.5.2
Squid-Cache Squid=3.5.3
Squid-Cache Squid=3.5.4
Squid-Cache Squid=3.5.5
Squid-Cache Squid=3.5.6
Squid-Cache Squid=3.5.7
Squid-Cache Squid=3.5.8
Squid-Cache Squid=3.5.9
Squid-Cache Squid=3.5.10
Squid-Cache Squid=3.5.11
Squid-Cache Squid=3.5.12
Squid-Cache Squid=3.5.13
Squid-Cache Squid=3.5.14
Squid-Cache Squid=3.5.15
Squid-Cache Squid=3.5.16
Squid-Cache Squid=4.0.1
Squid-Cache Squid=4.0.2
Squid-Cache Squid=4.0.3
Squid-Cache Squid=4.0.4
Squid-Cache Squid=4.0.5
Squid-Cache Squid=4.0.6
Squid-Cache Squid=4.0.7
Squid-Cache Squid=4.0.8

Event History

Apr 25, 2016
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2016-4051?

CVE-2016-4051 is classified as a high-severity vulnerability due to its potential to allow denial of service or arbitrary code execution.

2

How do I fix CVE-2016-4051?

To remediate CVE-2016-4051, upgrade to Squid versions 3.5.17 or later, or 4.0.9 or later.

3

Which versions of Squid are affected by CVE-2016-4051?

CVE-2016-4051 affects Squid versions 2.x, 3.x before 3.5.17, and 4.x before 4.0.9.

4

What kind of attacks can be executed using CVE-2016-4051?

Attackers can exploit CVE-2016-4051 to launch denial of service attacks or execute arbitrary code on vulnerable servers.

5

Is CVE-2016-4051 exploitable remotely?

Yes, CVE-2016-4051 can be exploited remotely by sending crafted data to the vulnerable cachemgr.cgi tool.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203