|
Squid Username Whitespace Security Bypass Issue
|
|
Secunia Advisory:
|
SA13843
|
|
|
Release Date:
|
2005-01-19
|
|
Last Update:
|
2005-02-07
|
|
Popularity:
|
10,367 views
|
|
|
Critical:
|
Less critical
|
|
Impact:
|
Security Bypass
|
|
Where:
|
From local network
|
|
Solution Status:
|
Vendor Patch
|
|
| Software: | Squid 2.x
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities 
|
|
| CVE reference: | CVE-2005-0173
|
|
Description:
A security issue has been reported in Squid, which can be exploited by malicious users to bypass certain security restrictions.
The issue is caused due to some LDAP implementations ignoring leading/trailing whitespaces in usernames. This can be exploited to bypass certain ACLs based on usernames or trick some log analysis by supplying a username with a whitespace in the beginning or end during the authentication process.
The vulnerability has been reported in version 2.5 and prior.
Solution:
Apply patch for 2.5.STABLE7:
http://www.squid-cache.org/Versions/v...s/squid-2.5.STABLE7-ldap_spaces.patch
Provided and/or discovered by:
Reported by vendor.
Changelog:
2005-02-03: Added CVE reference.
2005-02-07: Added link to US-CERT vulnerability note.
Original Advisory:
http://www.squid-cache.org/Versions/v2/2.5/bugs/#squid-2.5.STABLE7-ldap_spaces
Other References:
US-CERT VU#924198:
http://www.kb.cert.org/vuls/id/924198
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
