Vulnerability Note VU#924198

Squid LDAP authentication routines fail to check for invalid input

Original Release date: 04 Feb 2005 | Last revised: 11 Feb 2005


The Squid LDAP authentication routine squid_ldap_auth() fails to check for input characters, such as whitespace, that could be misused to possibly bypass access restrictions.


Squid functions as a web proxy and cache application for a number of protocols, and includes support for lightweight directory access protocol (LDAP) authentication. However, the squid_ldap_auth() function does not properly check for and sanitize input containing whitespace. This may allow remote attackers to log in using variants of existing user names, leading to bypass of security restrictions or creation of arbitrary accounting data.


Remote attackers may be able to gain elevated privileges or could pollute accounting data with invalid entries. This flaw is platform independent.


Apply an update

Administrators should obtain an updated version of Squid from their vendor if LDAP authentication is used.

Team Squid has created a patch for the current release version of Squid: squid-2.5.STABLE7-ldap_spaces.patch

This flaw has been patched in Squid 2.5.STABLE8-RC4. More details are available in the Squid Bugzilla bug #1187.

Squid administrators may either disable LDAP authentication or block usernames containing whitespace as a workaround.

Systems Affected (Learn More)

VendorStatusDate NotifiedDate Updated
SquidAffected-04 Feb 2005
If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A



Thanks to Team Squid for reporting this vulnerability, who in turn credit Andrew P with the discovery of this flaw.

This document was written by Ken MacInnis based primarily on information provided by Team Squid.

Other Information

  • CVE IDs: CAN-2005-0173
  • Date Public: 17 Jan 2005
  • Date First Published: 04 Feb 2005
  • Date Last Updated: 11 Feb 2005
  • Severity Metric: 6.30
  • Document Revision: 24


If you have feedback, comments, or additional information about this vulnerability, please send us email.