Security Update for squid3

squid3 Updated 02 Oct 2025

Summary

16/05/2016
N/A
Yes i
Unrated
Not published

DLA-478-1: squid3 - security update. Affects squid3 versions < 3.1.20-2.2+deb7u5. Fixed in 3.1.20-2.2+deb7u5. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Squid3 is a popular caching proxy that is widely used to improve web performance by caching frequently accessed web content. It acts as an intermediary between clients and servers, storing copies of web pages and resources to serve them quickly to clients upon request. However, several security vulnerabilities have been discovered in Squid3, which could potentially be exploited by attackers to compromise the system or perform denial of service attacks.

Vulnerability Detail

The vulnerabilities in Squid3 include:

  1. CVE-2016-4051: A buffer overflow vulnerability in Squid cachemgr.cgi allows remote attackers to execute arbitrary code or cause a denial of service (DoS) by providing malicious inputs.

  2. CVE-2016-4052: A buffer overflow vulnerability in Squid makes it vulnerable to a DoS attack when processing ESI responses.

  3. CVE-2016-4053: Squid is vulnerable to public information disclosure of the server stack layout when processing ESI responses.

  4. CVE-2016-4054: Squid is vulnerable to remote code execution when processing ESI responses.

  5. CVE-2016-4554: Squid is vulnerable to a header smuggling attack that could lead to cache poisoning and bypass of same-origin security policy.

  6. CVE-2016-4555 and CVE-2016-4556: Squid is vulnerable to a DoS attack when processing ESI responses due to incorrect pointer handling and reference counting.

These vulnerabilities pose a significant risk to the security and stability of systems running Squid3.

How To Fix

Minimum fixed version

3.1.20-2.2+deb7u5

This is the first release that contains the fix.

sudo apt-get install --only-upgrade squid3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There are no specific workarounds mentioned for these vulnerabilities. It is crucial to apply the security update as soon as possible to mitigate the risks associated with these vulnerabilities.

Conclusion

The vulnerabilities in Squid3 can have severe consequences for the security and stability of systems. It is crucial to apply the recommended security update to protect against potential attacks. For further support and assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for squid3 →

Share this vulnerability

FAQ

Squid3 is a caching proxy that improves web performance by storing copies of web pages and resources to serve them quickly to clients upon request.

These vulnerabilities can allow attackers to execute arbitrary code, cause denial of service, disclose sensitive information, and bypass security policies.

To fix these vulnerabilities, upgrade to the latest version of Squid3 (3.1.20-2.2+deb7u5 for Debian 7 Wheezy).

No specific workarounds are mentioned for these vulnerabilities. It is recommended to apply the security update.

You can obtain the updated packages from the official Debian repositories or the Squid website.

Related vulnerabilities

Recent vulnerabilities recorded for squid3.

How To Fix

Minimum fixed version

3.1.20-2.2+deb7u5

This is the first release that contains the fix.

sudo apt-get install --only-upgrade squid3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback