Squid - Header Smuggling Attack Vulnerability

squid Updated 02 Oct 2025

Summary

24/07/2016
N/A
Yes i
Unrated
Not published

DLA-558-1: squid - security update. Affects squid versions < 2.7.STABLE9-4.1+deb7u2. Fixed in 2.7.STABLE9-4.1+deb7u2. 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Squid is a caching proxy that is widely used to improve web server performance by caching frequently accessed web content. It acts as an intermediary between clients and servers, storing copies of web pages and serving them to clients upon request. Squid is a popular choice for organizations looking to optimize their network traffic and reduce bandwidth usage. However, the Squid version 2.7.STABLE9 is vulnerable to a header smuggling attack, which can lead to cache poisoning and bypass of same-origin security policy in Squid and some client browsers.

Vulnerability Detail

The vulnerability, identified as CVE-2016-4554, was discovered by Jianjun Chen. It allows an attacker to manipulate HTTP headers in a way that can deceive Squid and client browsers, potentially leading to cache poisoning and bypassing of same-origin security policy. This could enable an attacker to inject malicious content into the cache or bypass security restrictions, compromising the integrity and confidentiality of the system. The vulnerability affects Squid version 2.7.STABLE9.

How To Fix

Minimum fixed version

2.7.STABLE9-4.1+deb7u2

This is the first release that contains the fix.

sudo apt-get install --only-upgrade squid

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

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the fix mentioned above to mitigate the risk.

Conclusion

The Squid caching proxy version 2.7.STABLE9 is vulnerable to a header smuggling attack, which can lead to cache poisoning and bypass of same-origin security policy. It is crucial to upgrade the Squid package to version 2.7.STABLE9-4.1+deb7u2 or later to mitigate the risk. No known workaround is available for this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for squid →

Share this vulnerability

FAQ

Squid is a caching proxy that improves web server performance by caching frequently accessed web content.

A header smuggling attack is a technique used by attackers to manipulate HTTP headers in a way that can deceive the proxy server and client browsers.

Cache poisoning is a type of attack where an attacker injects malicious content into the cache, which is then served to clients, compromising their security.

The same-origin security policy is a security mechanism that restricts how a document or script loaded from one origin can interact with resources from another origin.

You can use Vulert's playground (https://vulert.com/scanner) to check if your Squid installation is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will analyze the dependencies and alert you if any vulnerabilities are found.

Related vulnerabilities

Recent vulnerabilities recorded for squid.

How To Fix

Minimum fixed version

2.7.STABLE9-4.1+deb7u2

This is the first release that contains the fix.

sudo apt-get install --only-upgrade squid

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