OWASP Top 10 for .NET devs part 8: Failure to Restrict URL Access(www.troyhunt.com)
submitted by 
troyhunt(831) 9 months, 25 days ago
What makes this particular risk so dangerous is that not only can it be used to very, very easily exploit an application, it can be done so by someone with no application security competency – it’s simply about accessing a URL they shouldn’t be.
On the positive side, this is also a fundamentally easy exploit to defend against. ASP.NET provides both simple and efficient mechanisms to authenticate users and authorise access to content. In fact the framework wraps this up very neatly within the provider model which makes securing applications an absolute breeze.
|category: Security
|Views: 19
tags:
Security another
Everyones tags:
Your Tags: