Kerio WinRoute Firewall Discloses Authentication Data to Remote Sites When Using Proxy Authentication
|
|
SecurityTracker Alert ID: 1008244 |
|
SecurityTracker URL: http://securitytracker.com/id/1008244
|
|
CVE Reference:
GENERIC-MAP-NOMATCH
(Links to External Site)
|
Date: Nov 19 2003
|
Impact:
Disclosure of authentication information
|
Exploit Included: Yes
|
Version(s): 5.10
|
Description:
A vulnerability was reported in the Kerio WinRoute Firewall software. A remote web server may be able to obtain a target user's username and password.
Alexander Antipov and 3APA3A reported that if proxy authentication is used, the firewall software may leak authentication credentials to remote users. The firewall software will reportedly send a slightly modified version of the target user's Proxy-Authorization header to any site that the target user visits. According to the report, the firewall will replace the first character with an 'X' character, as shown:
Xroxy-Authorization: Basic dGVzdDp0ZXN0aW5n
The username and password are Base64 encoded.
|
Impact:
A remote user (acting as a web server) may be able to obtain the target user's username and password.
|
Solution:
No solution was available at the time of this entry.
The author of the report indicates that, as a workaround, you can disable proxy authentication.
|
Vendor URL: www.kerio.com/kwf_home.html (Links to External Site)
|
Cause:
Access control error
|
Underlying OS:
Windows (Any)
|
|
Message History:
This archive entry has one or more follow-up message(s) listed below.
|
Source Message Contents
|
Date: Wed, 19 Nov 2003 19:06:56 +0300
Subject: [Full-Disclosure] [securitylab.ru & security.nnov] Kerio Winroute Firewall Xroxy problem
|
Application: Kerio Winroute Firewall 5.10
Vendor: Kerio Technologies Inc.
Vendor Site: http://www.kerio.com
Remote: Yes
Exploitable: Yes
Risk level: Critical (if proxy requires authentication)
Authors: Alexander Antipov & 3APA3A (aka Pig Killer)
Authors Sites: http://www.securitylab.ru http://www.security.nnov.ru
Intro:
Winroute is most popular SOHO software firewall/router/Proxy solution
for Windows platform.
Vulnerability:
During troubleshooting of Winroute a security related problem was
discovered allowing remote website to obtain cleartext credentials
(username:password) of WinRoute user.
Details:
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 exmple .gif, html, 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 cleartext (NTLM and Kerberos
probably is not supported by WinRoute). If WinRoute uses windows
authentication this credentials contain domain account information.
As a result, any webserver 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
Greets:
to Ink-Visitor who still awaiting for his document from Pig.
--
http://www.security.nnov.ru
/\_/\
{ , . } |\
+--oQQo->{ ^ }<-----+ \
| ZARAZA U 3APA3A } You know my name - look up my number (The Beatles)
+-------------o66o--+ /
|/
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
|
|
