[NT] Kerio WinRoute Firewall Account Information Leak

• Previous message: SecuriTeam: "[EXPL] OpenBSD exec_ibcs2_coff_prep_zmagic() Kernel Stack Overflow"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

To: list@securiteam.com
Date: 19 Nov 2003 18:25:59 +0200

The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion

The SecuriTeam alerts list - Free, Accurate, Independent.

Get your security news from a reliable source.
http://www.securiteam.com/mailinglist.html

- - - - - - - - -

  Kerio WinRoute Firewall Account Information Leak
------------------------------------------------------------------------

SUMMARY

 <http://www.kerio.com> WinRoute is "most popular SOHO software
firewall/router/Proxy solution for Windows platform". During
troubleshooting of WinRoute a security related problem was discovered
allowing remote websites to obtain clear text credentials
(username:password) of WinRoute user.

DETAILS

Vulnerable systems:
 * Kerio WinRoute Firewall version 5.10

WinRoute has extremely weak functionality as a proxy server. It doesn't
rebuild request sent by browser. Instead, it only changes Proxy- related
header by substituting fist character to X (So, for example,
Proxy-Connection header becomes Xroxy-Connection: in outgoing request). It
leads to few troubles. First, it leaks HTTP established connections. Every
file (for example .gif, html, and jpg) from web server requires separate
connection resulting in performance degradation. But, of cause, security
related problem is in handling Proxy-Authorization: header sent by
browser. Browser sends this header with every request in a case proxy
server requires authentication. This header contains base64-encoded
username and password of proxy user in clear text (NTLM and Kerberos
probably is not supported by WinRoute). If WinRoute uses windows
authentication this credentials contain domain account information.

As a result, any web server visited by WinRoute user can track his proxy
username and password by Xroxy-Authorization: header (X because first
character is changed).

For example:
 Xroxy-Authorization: Basic dGVzdDp0ZXN0aW5n (test:testing).

Workaround:
Disable proxy authentication.

ADDITIONAL INFORMATION

The information has been provided by Alexander Antipov and 3APA3A.

========================================

This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to: list-unsubscribe@securiteam.com
In order to subscribe to the mailing list, simply forward this email to: list-subscribe@securiteam.com

====================
====================

DISCLAIMER:
The information in this bulletin is provided "AS IS" without warranty of any kind.
In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.

• Previous message: SecuriTeam: "[EXPL] OpenBSD exec_ibcs2_coff_prep_zmagic() Kernel Stack Overflow"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]