Overview
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.
Description
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. |
Impact
Remote attackers may be able to gain elevated privileges or could pollute accounting data with invalid entries. This flaw is platform independent. |
Solution
Apply an update Administrators should obtain an updated version of Squid from their vendor if LDAP authentication is used. |
Squid administrators may either disable LDAP authentication or block usernames containing whitespace as a workaround. |
Vendor Information
CVSS Metrics
| Group | Score | Vector |
|---|---|---|
| Base | ||
| Temporal | ||
| Environmental |
References
Acknowledgements
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: | CVE-2005-0173 |
| Severity Metric: | 6.30 |
| Date Public: | 2005-01-17 |
| Date First Published: | 2005-02-04 |
| Date Last Updated: | 2005-02-11 22:01 UTC |
| Document Revision: | 25 |