Bad security decisions
In this day when security on the Internet is at the forefront of concerns, I’m constantly shocked to see what some web developers are putting out into the open. For obvious reasons, I’m not going to point out who is doing this, but I would like to point out a bad practice that should be common sense to avoid but for some reason is not.
I had logged into the system and was submitting a payment via electronic check. The screen I got to had remembered information about my account from a previous transaction and asked if I wanted to use the same account. I said yes. I was then taken to a page that asked me to confirm my account number before proceeding. This isn’t a bad practice, but the way it was implemented was horrible. There was a password input field, filled in with my account number, followed by another input field asking me to re-enter the number. So there’s a field with all stars above a field that shows the numbers as I type…interesting design.
As I looked at this I got a bad feeling in the pit of my stomach and I thought to myself, “they wouldn’t really have been dumb enough to fill in the password field with my full account number, would they?” I quickly viewed source to see…my account number had been output into the password field as static HTML. This weird UI was all in the name of security but ultimately, if someone had gotten in there by signing in as me, they would have had my bank account number in no time flat. Needless to say, that’s the last time I do business online with that particular site.
Disclaimer: Any viewpoints and opinions expressed in this article are those of Nicholas C. Zakas and do not, in any way, reflect those of my employer, my colleagues, Wrox Publishing, O'Reilly Publishing, or anyone else. I speak only for myself, not for them.