Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Web-App-Sec
[Top] [All Lists]

RE: [WEB SECURITY] Importing large code piece into Javascript context wi

Subject: RE: [WEB SECURITY] Importing large code piece into Javascript context without SCRIPT SRC=...
Date: Fri, 14 Oct 2005 11:32:10 -0700
Now just combine this with a snazzy XSS virus, so I can have another good
reason to turn this monitor off and go read a book:)

Very impressive, Amit...

~Dain White

-----Original Message-----
From: Jeremiah Grossman [mailto:jeremiah@whitehatsec.com] 
Sent: Friday, October 14, 2005 11:15 AM
To: Amit Klein (AKsecurity)
Cc: websecurity@webappsec.org; webappsec@securityfocus.com
Subject: Re: [WEB SECURITY] Importing large code piece into Javascript
context without SCRIPT SRC=...



On Oct 14, 2005, at 11:05 AM, Amit Klein (AKsecurity) wrote:

On 14 Oct 2005 at 10:56, Jeremiah Grossman wrote:


Admittedly, I was a bit confused by what your trying to achieve with
code. So sticking the question at hand...

"Importing large code piece into Javascript context without SCRIPT
SRC" ...
I take to do not use the HTML syntax... <script src="http://foo/
file.js"></script>

Here's an idea..

1) DOM Programming
var js = document.createElement('script');
js.setAttribute('src', 'http://foo/file.js');
document.body.appendChild(js);

* same effect, but different style.



Not fair ;-)

This will not be allowed (I supposed) by Content-Restrictions that  
specify no external code
(see the link in my original writeup). I think (hope...) that the  
Content-Restrictions
would apply to any JS executed, and to dynamically created HTMLs  
(such as the above).

And there's also a Content-Restriction against creating/modifying  
HTML nodes.

But yes, I suppose I should have clarified this. So thanks!


Oh ok, I see what you've done here now. This is quite clever. You're  
basically using the IFRAME URL as a source for receiving JS code,  
which you evaluate later when it becomes available. Nice.

In my Phishing w/ Superbait talk, I used a similar technique in  
reverse to pass large amounts of data off-domain. 2K blocks at a time.


Regards,

Jeremiah-









---------------------------------------------------------------------
The Web Security Mailing List
http://www.webappsec.org/lists/websecurity/

The Web Security Mailing List Archives
http://www.webappsec.org/lists/websecurity/archive/

<Prev in Thread] Current Thread [Next in Thread>