full-disclosure - Re: Attacking the local LAN via XSS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Fri, 4 Aug 2006 13:52:32 +0100
From: "pdp (architect)" <pdp.gnucitizen@...glemail.com>
To: thor@...ypath.com
Cc: Zed Qyves <zqyves.spamtrap@...il.com>, full-disclosure@...ts.grok.org.uk
Subject: Re: Attacking the local LAN via XSS

this is a very good point. :) cheers for that

then the problem is not actually sending a HTTP POST request but
getting the result from it or even modifying the headers. None of the
modern browsers allows you to read the iframe source. Well, actually
it is more likely to get thins working on IE6...

on the other hand, most devices have some sort of authentication
mechanism... most likely HTTP Basic Auth... that needs to go to the
headers of the request and it is not possible to perform it HTML forms
unless unless you are using the XmlHttpRequest object from JavaScript.

thx

On 8/4/06, Thor Larholm <thor@...ypath.com> wrote:
> pdp (architect) wrote:
>
> > HTTP PORT is not possible on domain different from the current domain,
> > unless browser hacks is employed.
>
> I'm guessing you mean HTTP POST :)
>
> You can definitely POST any FORM to a third party domain without hacks
> just by calling the submit() method of your FORM which targets a hidden
> iframe. e.g.
>
> <iframe style="display:none" id="thirdparty" name="thirdparty"></iframe>
> <form name="myform" action="http://whatever.com/foo.bar" method="POST"
> target="thirdparty">
> <input type="text" name="username" value="r00t">
> <input type="text" name="password" value="default router password">
> </form>
> <script>document.myform.submit()</script>
>
> The sequence of events would be to 1) Identify the router, 2) POST a
> login request with known default logins and 3) POST a change request to
> e.g. disable security settings or open a trust relationship.
>
> The only time consuming part is gathering router identification traits
> and tailoring login and change requests to specific router vendors.
>
> --
> Thor Larholm
>

-- 
pdp (architect)
http://www.gnucitizen.org

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/