Security Update for squid3

squid3 Updated 02 Oct 2025

Summary

03/08/2015
N/A
Yes i
Unrated
Not published

DSA-3327-1: squid3 - security update. Affects squid3 versions < 3.1.20-2.2+deb7u3. Fixed in 3.1.20-2.2+deb7u3. 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 fully-featured web proxy cache that allows clients to access web content through a gateway proxy. It is widely used to improve web performance and provide caching capabilities. However, a vulnerability has been discovered in Squid3 when configured with cache_peer and operating on explicit proxy traffic. This vulnerability could allow remote clients to gain unrestricted access through a gateway proxy to its backend proxy.

Vulnerability Detail

The vulnerability in Squid3 arises from its incorrect handling of CONNECT method peer responses. When configured with cache_peer and operating on explicit proxy traffic, remote clients can exploit this flaw to bypass restrictions and gain unrestricted access to the backend proxy. This could potentially lead to unauthorized access to sensitive information or abuse of the proxy infrastructure.

How To Fix

Minimum fixed version

3.1.20-2.2+deb7u3

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 is no specific workaround mentioned for this vulnerability. Upgrading to the fixed versions is the recommended solution.

Conclusion

It is crucial to promptly upgrade your squid3 packages to the fixed versions to mitigate the risk of unauthorized access and abuse of the proxy infrastructure. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for squid3 →

Share this vulnerability

FAQ

Squid3 is a fully-featured web proxy cache that improves web performance and provides caching capabilities.

The vulnerability allows remote clients to bypass restrictions and gain unrestricted access to the backend proxy, potentially leading to unauthorized access or abuse of the proxy infrastructure.

To fix this vulnerability, upgrade your squid3 packages to the fixed versions mentioned in the advisory.

No specific workarounds are mentioned. Upgrading to the fixed versions is the recommended solution.

You can obtain the updated packages from the official Debian repositories or through package management tools like apt-get.

Related vulnerabilities

Recent vulnerabilities recorded for squid3.

How To Fix

Minimum fixed version

3.1.20-2.2+deb7u3

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