|
Blue Coat ProxySG SGOS Two Security Issues
|
|
Secunia Advisory:
|
SA18622
|
|
|
Release Date:
|
2006-02-01
|
|
Last Update:
|
2006-02-09
|
|
Popularity:
|
9,045 views
|
|
|
Critical:
|
Less critical
|
|
Impact:
|
Security Bypass
|
|
Where:
|
From remote
|
|
Solution Status:
|
Vendor Workaround
|
|
| OS: | Blue Coat Security Gateway OS (SGOS) 4.x
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
Dominique GREGOIRE has reported two security issues in Blue Coat ProxySG, which can be exploited by malicious people to bypass certain security restrictions.
1) The HTTP proxy does not properly enforce port number restrictions on the CONNECT method when content inspection rules are defined in a policy. This allows the CONNECT method to be used to connect to arbitrary ports.
The security issue affects SGOS version 4.1.X prior to 4.1.4. Other versions are unaffected.
2) An error in the handling of policy evaluation order causes rules in the VPM (Visual Policy Manager) policy to be evaluated first, followed by the Local file policy, and then the Central file policy, regardless of the configured evaluation order.
The security issue has been reported in Bluecoat ProxySG running SGOS version 4.1.2.1. Other versions may also be affected.
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
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.
|
