Dinis Cruz | 1 Aug 2005 10:08

Re: [VulnWatch] The Java applet sandbox and stateful firewalls

Is the Java Sandbox able to create outgoing connections on ports like 445?

Also, even if it is possible, if a service like MS-SQL is already binded 
to 1433, then wouldn't an error be thrown saying something like 'Port 
already in use'.

That said, this is a very interesting concept, and a real vulnerability 
in any 'stateful protected system' if one is able to create TCP (or UDP) 
packets with explicit return ports (I will try to replicate this in .NET 
and will post here my results)

Dinis Cruz
.Net Security Consultant

Florian Weimer wrote:

>The Java/Firewall vulnerability
>===============================
>
>Current version: <http://www.enyo.de/fw/security/java-firewall/>
>
>The Java sandbox for applets and stateful firewalls interact in a
>surprising way. As a result, external hosts can initiate TCP
>connections to supposedly protected network services.
>
>* Attack Requirements
>
>This is a passive attack. The attacker must lure the victim to a
>carefully crafted web page. The victim's web browser must download and
>execute the embedded Java applet. The victim's computer must offer
(Continue reading)

Florian Weimer | 1 Aug 2005 14:15
Picon

Re: [VulnWatch] The Java applet sandbox and stateful firewalls

* Dinis Cruz:

> Is the Java Sandbox able to create outgoing connections on ports like 445?
>
> Also, even if it is possible, if a service like MS-SQL is already binded 
> to 1433, then wouldn't an error be thrown saying something like 'Port 
> already in use'.

This doesn't matter because in the PORT command sent to the FTP-like
server, the applet can reference a port which is not controlled by the
applet.  No checks take place, and it's perfectly possible to specify
an already bound port.  The firewall has no way to know that the port
actually belongs to some other process on the host (not the applet/FTP
client), and the sendbox does not examine the contents of TCP data
transfers at all.

Some NAT devices restrict access to 445/TCP, 139/TCP and a few more
ports, but by its nature, this list is incomplete and does not cover
all problematic TCP ports.
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/


Gmane