First published: Thu Apr 28 2005(Updated: )
Squid 2.5.STABLE9 and earlier does not trigger a fatal error when it identifies missing or invalid ACLs in the http_access configuration, which could lead to less restrictive ACLs than intended by the administrator.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Squid Web Proxy Cache | =2.5.stable1 | |
Squid Web Proxy Cache | =2.5.stable2 | |
Squid Web Proxy Cache | =2.5.stable3 | |
Squid Web Proxy Cache | =2.5.stable4 | |
Squid Web Proxy Cache | =2.5.stable5 | |
Squid Web Proxy Cache | =2.5.stable6 | |
Squid Web Proxy Cache | =2.5.stable7 | |
Squid Web Proxy Cache | =2.5.stable8 | |
Squid Web Proxy Cache | =2.5.stable9 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2005-1345 is classified as a medium severity vulnerability due to misconfigured access control lists that can lead to unintended access permissions.
To fix CVE-2005-1345, ensure that your http_access configuration includes valid ACL rules and update to a version of Squid later than 2.5.STABLE9.
CVE-2005-1345 affects Squid versions 2.5.STABLE1 through 2.5.STABLE9.
The risks of CVE-2005-1345 include potential unauthorized access to resources due to ineffective access control.
Yes, CVE-2005-1345 can be exploited remotely as it involves the misconfiguration of access controls in the Squid proxy server.