Vulnerability Note VU#868219
Multiple vendors' HTTP content/virus scanners do not check data tunneled via HTTP CONNECT method
Multiple vendors' HTTP anti-virus and content filters do not inspect the contents of HTTP CONNECT method tunnels. As a result, viruses or other restricted HTTP content may not be blocked as specified by policy.
Many anti-virus and content filter products that are designed to inspect HTTP application data rely on HTTP proxy functionality to examine the contents of HTTP connections. In turn, HTTP proxy services commonly support the HTTP CONNECT method, which is designed to create a TCP connection that bypasses the normal application layer functionality of the proxy. Typically, the HTTP CONNECT method is used to tunnel HTTPS connections through an HTTP proxy. The application layer data in an HTTP CONNECT method tunnel is opaque to the proxy service. The default configurations of many HTTP proxy services allow arbitrary TCP connections to be made using the HTTP CONNECT method [VU#150227].
As most HTTP proxy services ignore the HTTP data contained within an HTTP CONNECT method tunnel, so do most HTTP anti-virus and content scanners. As a result, it may be possible to create an HTTP CONNECT method tunnel through a vulnerable HTTP anti-virus or content scanner and transfer viruses or other restricted HTTP content.
A malicious actor may be able to bypass HTTP anti-virus software and HTTP content restrictions by transferring data via an HTTP CONNECT method tunnel.
Systems Affected (Learn More)
|Vendor||Status||Date Notified||Date Updated|
|Trend Micro||Affected||-||15 Apr 2002|
|F-Secure||Not Affected||19 Apr 2002||05 Jun 2002|
|F5 Networks||Not Affected||19 Apr 2002||28 May 2002|
|Hewlett-Packard Company||Not Affected||19 Apr 2002||29 May 2002|
|Sophos||Not Affected||19 Apr 2002||30 May 2002|
CVSS Metrics (Learn More)
The CERT/CC thanks Peter Bieringer and AERAsec Network Services and Security GmbH for information used in this document.
This document was written by Art Manion.
- CVE IDs: Unknown
- Date Public: 22 Feb 2002
- Date First Published: 15 Oct 2002
- Date Last Updated: 15 Oct 2002
- Severity Metric: 8.69
- Document Revision: 18
If you have feedback, comments, or additional information about this vulnerability, please send us email.