bugtraq - Re: ASP.NET __VIEWSTATE crypto validation prone to replay attacks

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1e89feb305050514177dcf0e27@mail.gmail.com>
Date: Thu, 5 May 2005 23:17:10 +0200
From: Michal Zalewski <lcamtuf@...il.com>
To: bugtraq@...urityfocus.com
Subject: Re: ASP.NET __VIEWSTATE crypto validation prone to replay attacks

I would also like to point all concerned to an excellent post about
replay attacks on __VIEWSTATE; the post is by Scott Mitchell, the guy
who authored the MSDN article I initially referred to [1]:

http://scottonwriting.net/sowblog/posts/3747.aspx

His article is aimed at developers; Scott explains the issue I
reported in a way that makes it perhaps more clear why putting user
ID, session ID, or other similar data in __VIEWSTATE is not a remedy
by itself, and why reposting __VIEWSTATE is dangerous despite target
script location checks.

[1] http://msdn.microsoft.com/library/en-us/dnaspp/html/viewstate.asp

Cheers,
/mz