|
Vulnerability Report: Squid 2.x
|
This vulnerability report for Squid 2.x contains a complete overview of all Secunia advisories affecting it. You can use this vulnerability report to ensure that you are aware of all vulnerabilities, both patched and unpatched, affecting this product allowing you to take the necessary precautions.
If you have information about a new or an existing vulnerability in Squid 2.x then you are more than welcome to contact us.
|
|
|
|
|
Vendor, Links, and Unpatched Vulnerabilities
| Vendor |
Squid
|
|
|
Product Link
|
View Here (Link to external site)
|
|
|
Affected By
|
24 Secunia advisories
22 Vulnerabilities
|
|
|
Monitor Product
|
Receive alerts for this product
|
|
|
Unpatched
|
8% (2 of 24 Secunia advisories)
|
|
Most Critical Unpatched
The most severe unpatched Secunia advisory affecting Squid 2.x, with all vendor patches applied, is rated Less critical  .
|
|
|
|
|
|
13 Secunia Advisories in 2005
|
Secunia has issued a total of 13 Secunia advisories in 2005 for Squid 2.x. Currently, 0% (0 out of 13) are marked as unpatched.
More information about the specific Secunia advisories affecting Squid 2.x can be found below. Each Secunia advisory is enclosed by a box highlighted with a color representing its current patch status. You can read the complete Secunia advisories for thorough descriptions of the issues covered and for solution suggestions by clicking either the Secunia advisory title or the "Read More" links available for each Secunia advisory.
|
|
|
|
|
|
Release Date:
2005-10-20 |
Secunia Advisory ID:
SA17271 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
DoS
|
Where:
From remote |
|
Short Description:
M.A.Young has reported a vulnerability in Squid, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date:
2005-09-30 |
Secunia Advisory ID:
SA16992 |
Solution Status:
Vendor Patch |
|
Criticality:
 |
Impact:
DoS
|
Where:
From remote |
|
Short Description:
Mike Diggins has reported a vulnerability in Squid, which potentially can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date:
2005-09-07 |
Secunia Advisory ID:
SA16708 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
DoS
|
Where:
From remote |
|
Short Description:
Nickolay has reported a vulnerability in Squid, which potentially can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date:
2005-09-02 |
Secunia Advisory ID:
SA16674 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
DoS
|
Where:
From remote |
|
Short Description:
Alex Masterov has reported a vulnerability in Squid, which potentially can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date:
2005-05-11 |
Secunia Advisory ID:
SA15294 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
Spoofing
|
Where:
From local network |
|
Short Description:
A vulnerability has been reported in Squid, which can be exploited by malicious people to spoof DNS lookups. [Read More]
|
|
|
|
|
|
Release Date:
2005-04-29 |
Secunia Advisory ID:
SA15093 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
Manipulation of data
|
Where:
From local network |
|
Short Description:
Steve Orrin has reported a vulnerability in Squid, which can be exploited by malicious people to poison the web proxy cache. [Read More]
|
|
|
|
|
|
Release Date:
2005-03-03 |
Secunia Advisory ID:
SA14451 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
Exposure of sensitive information
|
Where:
From remote |
|
Short Description:
A security issue has been reported in Squid, which may disclose sensitive information to malicious people. [Read More]
|
|
|
|
|
|
Release Date:
2005-02-14 |
Secunia Advisory ID:
SA14271 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
DoS
|
Where:
From remote |
|
Short Description:
A vulnerability has been reported in Squid, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date:
2005-02-01 |
Secunia Advisory ID:
SA14091 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
Manipulation of data
|
Where:
From remote |
|
Short Description:
A security issue has been reported in Squid, which potentially can be exploited by malicious people to pollute the cache. [Read More]
|
|
|
|
|
|
Release Date:
2005-01-31 |
Secunia Advisory ID:
SA14076 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
DoS
|
Where:
From local network |
|
Short Description:
FSC Vulnerability Research Team has reported a vulnerability in Squid, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
|
|
|
Release Date:
2005-01-19 |
Secunia Advisory ID:
SA13843 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
Security Bypass
|
Where:
From local network |
|
Short Description:
A security issue has been reported in Squid, which can be exploited by malicious users to bypass certain security restrictions. [Read More]
|
|
|
|
|
|
Release Date:
2005-01-13 |
Secunia Advisory ID:
SA13825 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
DoS
System access
|
Where:
From remote |
|
Short Description:
infamous41md has reported two vulnerabilities in Squid, which can be exploited by malicious people to cause a DoS (Denial of Service) or potentially compromise a vulnerable system. [Read More]
|
|
|
|
|
|
Release Date:
2005-01-11 |
Secunia Advisory ID:
SA13789 |
Solution Status:
Vendor Patch |
|
Criticality:
|
Impact:
DoS
|
Where:
From local network |
|
Short Description:
A vulnerability have been reported in Squid, which can be exploited by malicious people to cause a DoS (Denial of Service). [Read More]
|
|
|
