CVE-2005-0175: Medium severity Squid Squid vulnerability
Published Feb 6, 2005
·Updated
Squid 2.5 up to 2.5.STABLE7 allows remote attackers to poison the cache via an HTTP response splitting attack.
Affected Software
16 affected components
Squid Squid=2.5_stable9
Squid Squid=2.5_.stable3
Squid Squid=2.5.stable5
Squid Squid=2.5_stable3
Squid Squid=2.5.stable3
Squid Squid=2.5.6
Squid Squid=2.5.stable1
Squid Squid=2.5_.stable5
Squid Squid=2.5.stable6
Squid Squid=2.5_.stable6
Squid Squid=2.5.stable4
Squid Squid=2.5.stable2
Squid Squid=2.5_.stable1
Squid Squid=2.5_.stable4
Squid Squid=2.5_stable4
Squid Squid=2.5.stable7
Remediation
Patch Available
Patch Available
Patch Available
Patch Available
Event History
Feb 6, 2005
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2005-0175?
The severity of CVE-2005-0175 is classified as high due to its potential for cache poisoning.
2
How do I fix CVE-2005-0175?
To fix CVE-2005-0175, upgrade to Squid version 2.5.STABLE8 or later.
3
Which versions of Squid are affected by CVE-2005-0175?
CVE-2005-0175 affects Squid versions 2.5 up to 2.5.STABLE7.
4
What type of attack does CVE-2005-0175 involve?
CVE-2005-0175 involves an HTTP response splitting attack that can lead to cache poisoning.
5
Can CVE-2005-0175 affect my web security?
Yes, CVE-2005-0175 can significantly compromise web security by allowing attackers to manipulate cached content.