Squid vulnerabilitiesNone on the known-exploited list.
Squid has 41 published vulnerabilities across 3 products in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Squid, with 37. If you run Squid software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Squid products have the most vulnerabilities?
Squid leads with 37 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Squid vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Squid's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Squid flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 72%CVE-2009-0478Medium
Squid 2.7 to 2.7.STABLE5, 3.0 to 3.0.STABLE12, and 3.1 to 3.1.0.4 allows remote attackers to cause a denial of service via an HTTP request with an invalid version number, which triggers a reachable assertion in (1)...
- 70%CVE-2005-0241Medium
The httpProcessReplyHeader function in http.c for Squid 2.5-STABLE7 and earlier does not properly set the debug context when it is handling "oversized" HTTP reply headers, which might allow remote attackers to poison...
- 69%CVE-2005-0095Medium
The WCCP message parsing code in Squid 2.5.STABLE7 and earlier allows remote attackers to cause a denial of service (crash) via malformed WCCP messages with source addresses that are spoofed to reference Squid's home...
- 50%CVE-2005-0174Medium
Squid 2.5 up to 2.5.STABLE7 allows remote attackers to poison the cache or conduct certain attacks via headers that do not follow the HTTP specification, including (1) multiple Content-Length headers, (2) carriage...
- 41%CVE-2005-0446Medium
Squid 2.5.STABLE8 and earlier allows remote attackers to cause a denial of service (crash) via certain DNS responses regarding (1) Fully Qualified Domain Names (FQDN) in fqdncache.c or (2) IP addresses in ipcache.c,...
- 41%CVE-2005-0175Medium
Squid 2.5 up to 2.5.STABLE7 allows remote attackers to poison the cache via an HTTP response splitting attack.
- 32%CVE-2005-0173High
squid_ldap_auth in Squid 2.5 and earlier allows remote authenticated users to bypass username-based Access Control Lists (ACLs) via a username with a space at the beginning or end, which is ignored by the LDAP server.
- 27%CVE-2007-1560Medium
The clientProcessRequest() function in src/client_side.c in Squid 2.6 before 2.6.STABLE12 allows remote attackers to cause a denial of service (daemon crash) via crafted TRACE requests that trigger an assertion error.
- 27%CVE-2007-6239Medium
The "cache update reply processing" functionality in Squid 2.x before 2.6.STABLE17 and Squid 3.0 allows remote attackers to cause a denial of service (crash) via unknown vectors related to HTTP headers and an Array...
- 20%CVE-2007-0247Medium
squid/src/ftp.c in Squid before 2.6.STABLE7 allows remote FTP servers to cause a denial of service (core dump) via crafted FTP directory listing responses, possibly related to the (1) ftpListingFinish and (2)...
All Squid products we track.
3 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Squid? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Squid 2.7 to 2.7.STABLE5, 3.0 to 3.0.STABLE12, and 3.1 to 3.1.0.4 allows remote attackers to cause a denial of service via an HTTP request with an invalid version number, which triggers a reachable assertion in (1) HttpMsg.c and (2) HttpStatusLine.c.
- Matched to
- Squid on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
Our catalogue lists 41 published vulnerabilities across 3 products and 153 versions from Squid.
None of Squid's vulnerabilities is on the list of flaws known to be exploited today.
Squid, with 37 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Squid products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.