<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-29433331</id><updated>2011-11-27T16:35:32.448-08:00</updated><category term='more-than-a-search-engine'/><category term='xss'/><category term='data mining'/><category term='data theft'/><category term='xss csrf history'/><title type='text'>Web App Security Journ(ey)al</title><subtitle type='html'>My journey in the field of Web Application Security.

© 2007-2008</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>31</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-29433331.post-8546546928118739428</id><published>2009-02-05T08:23:00.000-08:00</published><updated>2009-02-05T08:57:52.455-08:00</updated><title type='text'>Internet Explorer 8 Ad Blocking</title><summary type='text'>I recently downloaded Internet Explorer 8 RC1 and was playing with the InPrivate Filtering feature. I think that this feature could be used as an Ad Blocker. I converted the adblock plus filters into xml format understood by IE and imported them in the InPrivate Filtering settings. Many websites worked fine while some (e.g. yahoo mail) appeared to be broken. I am sure that with a little tweaking </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/8546546928118739428/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=8546546928118739428' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/8546546928118739428'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/8546546928118739428'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2009/02/internet-explorer-8-ad-blocking.html' title='Internet Explorer 8 Ad Blocking'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-4318337733634791664</id><published>2008-04-29T12:57:00.000-07:00</published><updated>2008-04-29T13:13:40.025-07:00</updated><title type='text'>Can Browser's Password Manager Be Used As Sign In Seal?</title><summary type='text'>Almost every user uses browser's password manager these days. You visit a site, enter password and ask your browser to remember it. The password manager is supposed to fill out user name and the password automatically when you go to the site again.This can be used to avoid phishing attacks. The first time you visit any domain, make sure that you have typed in the url correctly in the address bar.</summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/4318337733634791664/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=4318337733634791664' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/4318337733634791664'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/4318337733634791664'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2008/04/can-browsers-password-manager-be-used.html' title='Can Browser&apos;s Password Manager Be Used As Sign In Seal?'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-4224175153569100871</id><published>2008-03-08T17:53:00.000-08:00</published><updated>2008-03-12T23:39:40.603-07:00</updated><title type='text'>Web2Torrent : Let web pages host your files...</title><summary type='text'>This is for research and fun purpose only. Don't contaminate the web using this technique. Use the tool at your own risk.I just finished a POC implementation of what I call as Web2Torrent. It is not exactly a torrent as you will know after reading this post. It is just a funny way of storing your files on blogs, message forums, mailing lists etc. (Note: This is no rocket science)It consists of a </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/4224175153569100871/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=4224175153569100871' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/4224175153569100871'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/4224175153569100871'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2008/03/web2torrent-let-web-pages-host-your.html' title='Web2Torrent : Let web pages host your files...'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-8670355290085726112</id><published>2008-02-14T18:09:00.000-08:00</published><updated>2008-02-14T18:12:12.585-08:00</updated><title type='text'>Software Lawyers and Standardized License Agreements?</title><summary type='text'>I posted following on my class blog. I think this should be interesting idea to consider.After reading this post, I thought that we should standardize privacy policies and license agreements. Let me explain what exactly I mean by that.In class Dr. Chen expressed the need of having information in a machine readable format. For this purpose we mainly use standards like FOAF, OWL etc. Companies are </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/8670355290085726112/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=8670355290085726112' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/8670355290085726112'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/8670355290085726112'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2008/02/software-lawyers-and-standardized.html' title='Software Lawyers and Standardized License Agreements?'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-6871133052189993460</id><published>2007-12-20T21:07:00.000-08:00</published><updated>2007-12-20T21:36:39.897-08:00</updated><title type='text'>Your 'Private' Videos on Orkut Are NOT Private!</title><summary type='text'>Hmmm.. After a long time I have found something interesting to write about.Orkut now has a feature that allows you to set your videos and photos as private so that only your friends can see your videos and photos. Well its not implemented that well it seems.Referer Header is at fault this time. Youtube videos have links section below each video which lists links referring to the current video. It</summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/6871133052189993460/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=6871133052189993460' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/6871133052189993460'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/6871133052189993460'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/12/orkut-private-videos-are-not-private.html' title='Your &apos;Private&apos; Videos on Orkut Are NOT Private!'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-3333934197192055901</id><published>2007-09-09T18:09:00.000-07:00</published><updated>2007-09-09T18:35:47.447-07:00</updated><title type='text'>IE home page URL resulting in XSS?</title><summary type='text'>I am not able to phrase the title of this entry correctly, but this is what I have found....Copy the following link location and set it as your homepage in IE 7.COPY THIS LINKWhen you open a new window in IE, it echoes your home page url in the window which results into something similar to XSS.I am trying to find a way to exploit this (like automatically setting homepage and adding some </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/3333934197192055901/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=3333934197192055901' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/3333934197192055901'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/3333934197192055901'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/09/ie-home-page-url-resulting-in-xss.html' title='IE home page URL resulting in XSS?'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-5765052500577346900</id><published>2007-07-24T00:22:00.000-07:00</published><updated>2007-07-24T00:36:48.481-07:00</updated><title type='text'>Is it that easy to write desktop worms?</title><summary type='text'>Some days ago, a friend of mine wanted few documents from me. So I plugged his pen-drive into the USB slot. As the next obvious step, I opened the drive. And strange things started happening on my computer.First of all, I saw an executable file with its icon similar to that of a normal directory. The name of which was MicrosoftPowerPoint.exe. Note that I noticed the extension because luckily I </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/5765052500577346900/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=5765052500577346900' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/5765052500577346900'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/5765052500577346900'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/07/is-it-that-easy-to-write-desktop-worms.html' title='Is it that easy to write desktop worms?'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-1176211071867024719</id><published>2007-07-05T10:34:00.000-07:00</published><updated>2007-07-05T21:20:59.896-07:00</updated><title type='text'>IE - Guessing The Names Of The Fixed Drives On Your Computer</title><summary type='text'>DEMOWhile doing experiments with IE I observed another weird behavior. When I created an anchor tag with href="a:crap" like this, in the progress bar at the bottom IE showed "file:///a:crap". Now this is interesting. How could IE even try to guess the protocol unnecessarily?I went ahead with a new experiment: created iframes with src = a:crap. This time a 'page could not be displayed' error </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/1176211071867024719/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=1176211071867024719' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/1176211071867024719'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/1176211071867024719'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/07/ie-guessing-names-of-fixed-drives-on.html' title='IE - Guessing The Names Of The Fixed Drives On Your Computer'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-2484705647631384707</id><published>2007-06-23T10:20:00.000-07:00</published><updated>2007-06-23T10:45:32.992-07:00</updated><title type='text'>SSL tunneling using CONNECT method and its security implications</title><summary type='text'>Most of you know how CONNECT method is used by the client and the proxy to successfully tunnel an HTTPS connection without the proxy seeing the data. If you don't, then here is a quick description.The client sends a CONNECT request to the proxy asking it to connect to the specified destination.e.g. [1]CONNECT mail.google.com:443 HTTP/1.0User-agent: xyzThe proxy then connects to the destination </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/2484705647631384707/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=2484705647631384707' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/2484705647631384707'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/2484705647631384707'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/06/ssl-tunneling-using-connect-method-and.html' title='SSL tunneling using CONNECT method and its security implications'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-2147434325960334499</id><published>2007-05-23T08:11:00.000-07:00</published><updated>2007-05-23T08:30:25.724-07:00</updated><title type='text'>Bypassing WAF with full-width Unicode encoding</title><summary type='text'>This issue is in the news for past few days. If anyone wants to try it yourself, here is how you do it.If you want to try it out on IIS (.NET 1.x), here are the steps,response encoding is to be set to ISO-8859-1 usingin the config file (C:\WINDOWS\Microsoft.NET\Framework\vxxx\CONFIG\web.config). (Thanks to my colleague for setting this up)Here is the aspx file you can use,&lt;html&gt;/&lt;head&gt;&lt;/head&gt;&lt;</summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/2147434325960334499/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=2147434325960334499' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/2147434325960334499'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/2147434325960334499'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/05/bypassing-waf-with-full-width-unicode.html' title='Bypassing WAF with full-width Unicode encoding'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-3202374982289799400</id><published>2007-05-14T04:37:00.000-07:00</published><updated>2007-05-16T00:03:24.517-07:00</updated><title type='text'>XSS in eXceSS</title><summary type='text'>XSS in eXceSS is a page that shows various areas of the HTML page where user input can get echoed back. It takes the input via various get parameters and leads to different areas in the HTML page. E.g. parameter freehtml=ATTACK_VECTOR will place the injection in to the HTML body. There are more than 25 such parameters which lead to different XSS areas.Please read the usage notes on the page.In </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/3202374982289799400/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=3202374982289799400' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/3202374982289799400'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/3202374982289799400'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/05/xss-in-excess.html' title='XSS in eXceSS'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-1744608439073788307</id><published>2007-04-09T01:34:00.000-07:00</published><updated>2007-04-09T01:45:10.661-07:00</updated><title type='text'>Onetime url implementation broken this time</title><summary type='text'>After writing this horrible post and taking it back,  a fellow blogger (at least I consider him a fellow blogger)  reminded me that everyone makes mistakes. This helped me continue my pursuit to break onetime url.I'm confident this time. This one does work. If it does not, allow me more time :)Key is to 'Watch' the 'Unwatch'! :)&lt;script&gt; function uw (a,b,c){}document.location.watch("unwatch", </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/1744608439073788307/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=1744608439073788307' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/1744608439073788307'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/1744608439073788307'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/04/onetime-url-implementation-broken-this.html' title='Onetime url implementation broken this time'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-2108310866516606568</id><published>2007-04-06T00:10:00.000-07:00</published><updated>2007-04-07T01:44:23.308-07:00</updated><title type='text'>Onetime url implementation needs more server side protection</title><summary type='text'>Don't read this post. I should not have published it.I may be repeating things w.r.t. this here (it was hard to read the entire thread),But following anti-poc works as of today.&lt;script&gt;var wnd = window.open ("");wnd.document.open();wnd.document.write("&lt;head&gt;&lt;script&gt;window.setInterval(\"steal()\",5000);function steal(){alert(opener.location);}&lt;/" +"script&gt;&lt;/head&gt;&lt;body&gt;&lt;/body&gt;");wnd.document.close(</summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/2108310866516606568/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=2108310866516606568' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/2108310866516606568'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/2108310866516606568'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/04/onetime-url-implementation-needs-more.html' title='Onetime url implementation needs more server side protection'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-3132150593529760824</id><published>2007-03-26T23:22:00.000-07:00</published><updated>2007-03-30T22:33:24.649-07:00</updated><title type='text'>One time URLs broken for AJAX apps</title><summary type='text'>After finding the first obvious way to break  OneTimeURLPrototype , I want to present another possibility where it will fail.The prototype itself is not vulnerable, but if an AJAX app uses this prototype to get one time token, is likely to be vulnerable.Basis of this is that XMLHttpRequest constructor is not protected in the prototype.The key is to open a new window-2 from original window-1, </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/3132150593529760824'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/3132150593529760824'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/03/one-time-urls-broken-if-ajax-is-present.html' title='One time URLs broken for AJAX apps'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-4129114232463107087</id><published>2007-03-22T23:57:00.000-07:00</published><updated>2007-03-23T00:07:33.205-07:00</updated><title type='text'>Google.com using invalid certificate?</title><summary type='text'>Point your browser to https://google.com/adsenseOr they are not redirecting properly.</summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/4129114232463107087/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=4129114232463107087' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/4129114232463107087'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/4129114232463107087'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/03/googlecom-using-invalid-certificate.html' title='Google.com using invalid certificate?'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://bp0.blogger.com/_8AzgqUt4_kE/RgN8h2s0LQI/AAAAAAAAAAU/fNX5UayVh_I/s72-c/cert2.JPG' height='72' width='72'/><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-5201849522018443409</id><published>2007-03-20T22:11:00.000-07:00</published><updated>2007-03-20T22:22:56.237-07:00</updated><title type='text'>One time URLs first implementation broken!</title><summary type='text'>if(document.location.href.indexOf("rand=") &gt;= 0){var str = document.location.href; var re = /rand=([\d]+)/;var res = re.exec(str);if(res)alert("Token is " + res[1]);}This is w.r.t. http://onetimeurls.databasement.net/index.phpAs always, the developers think their code is bullet proof and actually it contains basic flaws. (No offence meant, I'm just being philosophical).Here is the POC on how to </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/5201849522018443409/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=5201849522018443409' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/5201849522018443409'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/5201849522018443409'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/03/one-time-urls-first-implementation.html' title='One time URLs first implementation broken!'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-1799529017164982572</id><published>2007-03-16T21:56:00.000-07:00</published><updated>2007-03-17T06:21:52.332-07:00</updated><title type='text'>Why Web Security is a Difficult Problem To Solve</title><summary type='text'>There has been a discussion on how common filters implemented to block XSS are likely to fail. The most common action taken against the user input is converting the characters that could possibly define a tag, event handler etc. into HTML entities. This allows for the input to be displayed correctly but without it being executed.E.g.&lt; is converted to &amp;lt;&gt; is converted to &amp;gt;&amp; is converted to &amp;</summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/1799529017164982572/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=1799529017164982572' title='5 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/1799529017164982572'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/1799529017164982572'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/03/why-web-security-is-hard-to-implement.html' title='Why Web Security is a Difficult Problem To Solve'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>5</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-1921070012438214595</id><published>2007-03-04T03:36:00.000-08:00</published><updated>2007-03-04T04:06:00.460-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='xss csrf history'/><title type='text'>History of XSS, CSRF</title><summary type='text'>I was searching for history of XSS and CSRF attacks. I was mostly interested in knowing when each of these was discovered. I found following posts which tried to point out an approximate year of discoveries of these two vulnerabilities.http://seclists.org/webappsec/2005/q4/0125.htmlhttp://www.webappsec.org/lists/websecurity/archive/2005-05/msg00003.htmlAccording to the first link, ("If I remember</summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/1921070012438214595/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=1921070012438214595' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/1921070012438214595'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/1921070012438214595'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/03/history-of-xss-csrf.html' title='History of XSS, CSRF'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-4807842041166268970</id><published>2007-03-01T09:43:00.000-08:00</published><updated>2007-03-01T09:52:56.848-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='xss'/><title type='text'>Is XSS in blogger applications serious enough</title><summary type='text'>As I was reading through some of my earlier posts, I came across this post. At the time when I wrote that one, I did not know what blogging was all about. Later when I started using it more and more, adding tools like sitemeter and adsense, I realized that being able to add scripts to your posts is fairly normal.But then was the post mentioned above totally useless? I don't think so. At the time </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/4807842041166268970/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=4807842041166268970' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/4807842041166268970'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/4807842041166268970'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/03/is-xss-in-blogger-applications-serious.html' title='Is XSS in blogger applications serious enough'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-3033983301226241586</id><published>2007-01-20T09:35:00.000-08:00</published><updated>2007-01-20T10:22:37.250-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='more-than-a-search-engine'/><category scheme='http://www.blogger.com/atom/ns#' term='data mining'/><category scheme='http://www.blogger.com/atom/ns#' term='data theft'/><title type='text'>Do you trust Google? (Humor, but an idea worth consideration)</title><summary type='text'>Imagine you have an excellent business idea, something as revolutionary as Newton's law of gravity. You want to file a patent for this idea in order to protect yourself. Whats the first step you will take?You are right!, You will go to our favorite search engine www.google.com and search if someone else has already published a similar idea. If you do not find anything on google, you will most </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/3033983301226241586/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=3033983301226241586' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/3033983301226241586'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/3033983301226241586'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2007/01/do-you-trust-google-humor-but-idea.html' title='Do you trust Google? (Humor, but an idea worth consideration)'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-116663540578827176</id><published>2006-12-20T09:18:00.000-08:00</published><updated>2007-01-05T01:18:41.510-08:00</updated><title type='text'>CSRF protection for the AJAX area of web applications</title><summary type='text'>I'll be using following terms throughout the article,AJAX area: Server side scripts which are mainly designed to process requests generated by client side scripts (AJAX)Non AJAX area: Other server side scriptsApplication: Sometimes the term will be used to refer to the JavaScript that gets executed.In an AJAX application, the user loads a normal HTML page in his browser. This page includes </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/116663540578827176/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=116663540578827176' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/116663540578827176'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/116663540578827176'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2006/12/csrf-protection-for-ajax-area-of-web.html' title='CSRF protection for the AJAX area of web applications'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-116530771161286086</id><published>2006-12-05T00:35:00.000-08:00</published><updated>2006-12-05T01:17:57.146-08:00</updated><title type='text'>Use of time delay technique for effective CSRFs</title><summary type='text'>I read Jeremiah Grossman's article on Browser Port Scanning without JavaScript.One point to note is that this is based on the time difference that is observed whenA host is upA host is downOne of the techniques of port scanning using javascript also relies on this time difference.Now look at comment that says "The purpose of CSRF is to perform actions on behalf of the current user but this user </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/116530771161286086/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=116530771161286086' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/116530771161286086'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/116530771161286086'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2006/12/use-of-time-delay-technique-for.html' title='Use of time delay technique for effective CSRFs'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-116054587419567955</id><published>2006-10-10T22:47:00.000-07:00</published><updated>2006-10-10T22:51:14.696-07:00</updated><title type='text'>My interpretation - Orkut vector</title><summary type='text'>Interpretation of this page with this injection string.Orkut user entered scrap text aswww.orkut.com/"gt;lt;/a&gt;&lt;img src="http://www.bandeirasanimadas.com/Asia/India/3dflagsdotcom_india_2fawm.gif" onload=alert(1)&gt;&lt;a style="display:none" href="Let's greet the independence of India. CHEERS!Look at the string BEFORE "Let's greet the independence of India. CHEERS!"Lets call it $USER_LINKThe string </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/116054587419567955/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=116054587419567955' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/116054587419567955'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/116054587419567955'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2006/10/my-interpretation-orkut-vector.html' title='My interpretation - Orkut vector'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-116046117475818945</id><published>2006-10-09T23:18:00.000-07:00</published><updated>2006-10-09T23:23:30.936-07:00</updated><title type='text'>URL decoded version</title><summary type='text'>www.orkut.com/"&gt;&lt;/a&gt;&lt;img src="http://www.bandeirasanimadas.com/Asia/India/3dflagsdotcom_india_2fawm.gif" onload=alert(1)&gt;&lt;a style="display:none" href="Let's greet the independence of India. CHEERS!</summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/116046117475818945/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=116046117475818945' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/116046117475818945'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/116046117475818945'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2006/10/url-decoded-version.html' title='URL decoded version'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-116015711024647617</id><published>2006-10-06T10:51:00.000-07:00</published><updated>2006-10-06T10:59:37.766-07:00</updated><title type='text'></title><summary type='text'>Orkut XSS - silently fixed!On the 14th August , I got a scrap from my friend wishing me happy independence day (15 th).I noticed one interesting thing, I could see image of Indian flag along with the scrap.I quickly realized that something was wrong. Same scraps were floating around all over orkut that day. After modifying scrap text a little, I could verify that XSS did infact exist.When I </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/116015711024647617/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=116015711024647617' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/116015711024647617'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/116015711024647617'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2006/10/orkut-xss-silently-fixed-www.html' title=''/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-115374094560611460</id><published>2006-07-24T04:14:00.000-07:00</published><updated>2006-07-24T04:35:45.810-07:00</updated><title type='text'></title><summary type='text'>DIRB  I tried out this URL bruteforcer. The database it has looks impressive. It includes entries categorised in different text files. Although the test extension file looks unnecessary. It has all combinations of 3 alphabets e.g. aaa,aab,...aba...zzz. appended to "test.".Home pageDescription as on sourceforge:"DIRB - URL Bruteforcer: DIRB is a Web Content Scanner. It looks for hidden Web Objects</summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/115374094560611460/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=115374094560611460' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/115374094560611460'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/115374094560611460'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2006/07/dirb-i-tried-out-this-url-bruteforcer.html' title=''/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-115331307903226733</id><published>2006-07-19T05:43:00.000-07:00</published><updated>2006-07-21T04:35:27.803-07:00</updated><title type='text'></title><summary type='text'>PAROSParos is a well known tool used for testing web application related issues. It includes a spider that walks your application. There is a set of tests you can run which cover commonly found vulnerabilities - XSS, SQL injection.If you want to attack an application manually, you have a trap option which lets you modify the request that is sent out.I'm not sure if the spider is intelligent </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/115331307903226733/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=115331307903226733' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/115331307903226733'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/115331307903226733'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2006/07/paros-paros-is-well-known-tool-used.html' title=''/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-115329898923908548</id><published>2006-07-19T01:40:00.000-07:00</published><updated>2006-07-19T02:00:03.946-07:00</updated><title type='text'></title><summary type='text'>Springenwerk Security ScannerThis is a free XSS scanner available on web. With a few enhancements, this could make a quick scan of your applications possible. This type of scanner is useful for manual pen-testers when they have to try out loads of injection variations. Such a task is tedious to do manually and on each field in the application. This tool generates a report in a nice </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/115329898923908548/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=115329898923908548' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/115329898923908548'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/115329898923908548'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2006/07/springenwerk-security-scanner-this-is.html' title=''/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-115312195420328552</id><published>2006-07-17T00:35:00.000-07:00</published><updated>2006-07-17T00:41:14.520-07:00</updated><title type='text'></title><summary type='text'>Blogspot XSSI have accidentaly found a XSS vulnerability on blogspot. But later I found that someone has already reported it here. So there is no need to notify blogspot guys again.</summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/115312195420328552/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=115312195420328552' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/115312195420328552'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/115312195420328552'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2006/07/blogspot-xss-i-have-accidentaly-found.html' title=''/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-115311542527442276</id><published>2006-07-16T22:50:00.000-07:00</published><updated>2006-07-17T00:42:08.923-07:00</updated><title type='text'></title><summary type='text'>Did I find XSS vulnerability in .NET and PHP?This funny incident happened this week. I was too excited after Ifound a vulnerability in .NET security class. Yes, I wondered howeasily could I find it. I patted on my back for this amazing finding. Ithough I was gonna shock the entire world.Then I went on to trying the same method out on Apache-PHP. And voila! it worked too.I know you are curious to </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/115311542527442276/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=115311542527442276' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/115311542527442276'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/115311542527442276'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2006/07/did-i-find-xss-vulnerability-in.html' title=''/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-29433331.post-115200442964060991</id><published>2006-07-04T02:13:00.000-07:00</published><updated>2006-07-04T02:13:49.656-07:00</updated><title type='text'>Amazing XSS exploit tool</title><summary type='text'>http://xss-proxy.sourceforge.net/Many people think that XSS (cross site scripting) is not very dangerous. This tool explains why and how XSS can be used in order to retrieve sensitive information without knowing much about the web technologies. Anyone who just knows what XSS is, how to run a perl script (you just need to know how to run it, you need not know perl!) and the vulnerable site's user </summary><link rel='replies' type='application/atom+xml' href='http://wasjournal.blogspot.com/feeds/115200442964060991/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=29433331&amp;postID=115200442964060991' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/115200442964060991'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/29433331/posts/default/115200442964060991'/><link rel='alternate' type='text/html' href='http://wasjournal.blogspot.com/2006/07/amazing-xss-exploit-tool.html' title='Amazing XSS exploit tool'/><author><name>Kishor</name><uri>http://www.blogger.com/profile/03413161469042432636</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='27' height='32' src='http://2.bp.blogspot.com/-uPTC_XNQerw/Thqn6E3FYuI/AAAAAAAAAJI/XCJQW9GKHew/s220/Untitled.jpg'/></author><thr:total>1</thr:total></entry></feed>
