squid -- confusing results on empty acl declarations

Description:

Applying an empty ACL list results in unexpected behavior: anything will match an empty ACL list. For example,

The meaning of the configuration gets very confusing when we encounter empty ACLs such as

acl something src "/path/to/empty_file.txt"
http_access allow something somewhere

gets parsed (with warnings) as

http_access allow somwhere

And similarily if you are using proxy_auth acls without having any auth schemes defined.

References:

• CVE name CVE-2005-0194
• URL: <http://www.squid-cache.org/Versions/v2/2.5/bugs/#squid-2.5.STABLE7-empty_acls>
• URL: <http://www.squid-cache.org/bugs/show_bug.cgi?id=1166>

Affects:

• squid <2.5.7_5

Disclaimer: The data contained on this page is derived from the VuXML document, please refer to the the original document for copyright information. The author of portaudit makes no claim of authorship or ownership of any of the information contained herein.

If you have found a vulnerability in a FreeBSD port not listed in the database, please contact the FreeBSD Security Officer. Refer to "FreeBSD Security Information" for more information.