Skip to main content

ASP.NET MVC Identity–Registration

I was listening today to DotNetRocks episode 1109 with Troy Hunt, a well known security expert. In this episode Troy was sharing the following story(I summarized it):

“Some people claim that they have hacked DropBox or iCloud. But instead the only thing they did was trying out a list of available usernames and password(acquired from other hacks), until one of them works.

To make this more difficult for a hacker, it’s important that your application doesn’t expose any information if a specific email address is used inside your application or not. For example, on the login page when a user types a wrong email address to login, don’t say that the email address can not be found but give a more generic error mentioning that ‘username and/or password are incorrect’. Do the same thing on your forgot password page, don’t tell the users that the email address  can not be found but tell them that ‘a password reset mail is send to the specified email address’. Last place where you could accidently expose if an email address is used or not is on the registration page. Allow users to use any email address they want and don’t tell them if the email address is already in use or not.

You maybe lose some usability, but you gain a lot in terms of security”.

His explanation made me wonder if  the built-in authentication system in ASP.NET MVC is following all these recommendations.

  • Let’s first try to register a user with an email address that is already used:

image

That’s bad, on the registration page, you get a specific error if the email address is already in use. -1 for ASP.NET MVC… Bedroefde emoticon

  • Let’s now try to log in using a non existing email address:

image

Same error message for an existing and non-existing user. +1 for ASP.NET MVC… Glimlach

  • Let’s now try to reset our password:

image

image

Same message no matter if the email address exists in the application or not. +1 for ASP.NET MVC… Glimlach

Conclusion

2 out of 3 doesn’t sound bad, but one location where information about your users is exposed is one location too much…

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.