So – assuming you have CustomErrors not set to “Off” and and redirectmode set to “ResponseRewrite” – does this protect you from this vulnerability? Or is this irrelevant?
I have the following error when write this function in pyton
Traceback (most recent call last):
can any one please let me know t site for poet.py … i tried jar file for the same but its not working. want to give a try for python. an immediate help will be great.
@MrPrahalath See section D. of RFP policy and compare to MSRC: weird response, followed by months of no fix. Guess why people arent complying? See statements from veracode researchers etc as well
@randomgeocacher
The old hacker opinion seems to be: “Lets screw it up so that SOMEONE ELSE CAN HANDLE IT BETTER in the future”
0-Day:
No matter what form 0-Day takes (…if ever), it will inevitably consist of many many tiny “SOMEONE ELSE WILL HANDLE IT” moments. This can be seen in explosions and wars and other areas where people are afraid.
Since the internet is the internet only because everyone is using it, a person is either a part of the problem or a part of the solution.
@MrPrahalath papers published since 2002 define class of vulnerabilities. 8 years would satisfy “due time” for crypto vendors to remedy Padding Oracle attack?
And the CBC-R works cause ASP.NET does Encypt-Without-MAC, which you have to go back to medieval times for people not to know it is a vulnerability.
Microsoft failed in many ways here.
I don’t know when or if MSRC was notified, it is interesting that ASP.NET was omitted in the first papers by these guys. Was this really “0-day”?
@wydok
authentication mode=”Forms”
forms name=”.DOTNETNUKE” protection=”All” timeout=”120″ cookieless=”UseCookies” /
If you browse the source code, you can easily determine what they have put in the auth cookie.
If it had been closed source, you could achieve the same with reflection (or simply copying the cookie into a an app which decrypts the key).
Basically, ASP.NET Form Auth cookies are 100% f*cked once your keys are in the hands of the bad guys.
@wydok ASP.NET Form Authentication works that way. Regardless of what we might think about it, it is a design decision of Microsoft, DotNetNuke is just following “the standard way to do it”.
Why would anyone save information about a user’s login name or security access in a cookie? This should be set in the Session object instead. That way the only cookie set is the cookie that is the ASP.NET Session ID.
Okay, so this Poet tool using a bug in ASP.NET in how it handles padding, and uses a brute force method to send multiple requiests to an ASP.NET website until it gets a correct response and is able to use that to find the encryption key.
But how does POET then use that key to determine the proper cookie to set to give a user admin privledges? Is it based on the concept that .dotNetNuke uses a specific username as the superuser?
this is completly stupid !!!!
and have nothing to do with ASP.net
@coreyogburn Nothing in this world is perfect. This is something we all know. You can buy the most expensive car in the world and it *will* come with some imperfection. This is a fact. Timing and the order in which one does something is also an important factor in getting things right.
@coreyogburn momentary fame: This particular software “bug” or whatever you guys call it was exposed to the public *before* the relevant authorities were notified about it. This was the real security risk imo — with video instructions on youtube on how to go about breaking into an ASP.NET installation.
What part of this problem can cryptbe accept responsibility for? He just went “oops…” while everyone else was scrambling desperately to find a solution to the problem.
@MrPrahalath If this guy doesn’t find the problem and work towards fixing it, then somebody else will find the problem and work towards exploiting it. I hate to put words in your mouth, but it sounds like you’re saying “don’t look for a problem, focus on more important things.” With a foundation as widely accepted as ASP.Net, the problem is the important thing and it does need to be fixed.
OMG guys, this is absolutely perfect, I can’t say anything else, but congratulations!
@MrPrahalath That’s how security research progresses. This is good work.
The things people do for momentary fame. Get a life. Don’t you people have anything better to do than threatening the whole world? You guys have some serious skillz that could definitely be put to better use.
cryptbe, you and the hoax artists that presented this at ekoparty and made this video are clowns. Anyone who knows ASP.NET and DNN knows you rigged this for breakage. Your video shows plainly that the setup not only doesn’t follow best practices, but doesn’t even have the default DNN install protections in place. Quit claiming the MS work-around won’t work, and PROVE it.
fag. get rid of the gay music and maybe ill watch instead of thumbs down 5 seconds in.
You must be logged in to post a comment.
Comments
Leave a comment Trackback