The Picture above should give u a pretty good idea what this post is all about !
                                                                                                 if it dint then click here.

     No Jeff is not starting greekswithblogs, lol :) neither did he edit this home page I did, don't worry it was up for not more than few seconds (actually 5sec- up, snapshot'd, removed). so how did I do that ? well that's a secret!

When I discovered this, it was a little shocking but did give me a good understanding of .text and this flaw. This post applies to all blogs & blog servers working on .text, when homepage on say in geekswithblogs.net or weblogs.asp.net is displayed / created the server scans the recent / new posts of all the bloggers and posts them. That should imply that all the posts should stay in the blog post allocated area: {+} (i.e. all the settings and adjustments should apply only to my post and not to exceed its boundaries) but I have found it otherwise: +{+}+ which could result in direct editing of home page by any user, or probably even by anyone using html injecting thru the comment section* Unless fixed! consider this as a threat as there would be more of an evil mind acting on the homepage long before the administrator realizes it - since all these sites are automated
* section is not verified!

Snapshots of the things I was able to do/did by this flaw/bug/vulnerability.



I Have also found a similar bug on blogger.com few months ago, but that does not have any threat as u can only edit in your console used for blogging and not any public access page! it actually gives in an advantage for blogger. ( i used to have a search engine and few of my favorites blogs links over the console using this bug, before I got bored of it, am searching my 80GB Hard disk for its snapshot, its is quite a tuf job :) lol ).


Read My Security Blog for tips and posts on being secure online.

UMESH SECURITY BLOG
   www.secureblog.net