-
Website
http://consumerismcommentary.com/ -
Original page
http://www.consumerismcommentary.com/2007/04/11/turbotax-fixed-a-security-leak/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
¢entsiblelife
1 comment · 1 points
-
BDickson114
1 comment · 1 points
-
freeby50
2 comments · 1 points
-
ericabiz
4 comments · 12 points
-
Walt Breuninger
1 comment · 1 points
-
-
Popular Threads
I paid $450 last year for a local accountant to do my taxes, and am just not feeling it this year.
I did see the story about the security flaw and lots of enraged user responses as I was looking for a tip in the TurboTax forums, but I felt it was somewhat of an overreaction as well. After all, it's not like someone couldn't get all the same information *plus* someone's official signature and maybe even a free stamp for reuse just by intercepting paper tax forms on their way to the post office. If your own mailbox doesn't place you at risk, some disgruntled or paid off postal worker might.
Granted, I do think companies which handle our financial, medical, and other personal information should pursue every possible measure to keep this information safe, so maybe the scolding and bad PR help that. Or maybe they just cause companies to spend more on their own PR and the same on upgrades, programmer training and server support. Food for thought.
I was just amused by all the huffy people skulking off to paper-file their taxes so it'd be secure.
I think one of the other areas of risk are companies that store my data unencrypted on their servers.
I believe they need to make it mandatory for people to be able to put freezes on their credit. It seems crazy to me that we aren't allowed to do that permanently and with little effort.
I worked in online banking for 7 years and in all that time we only had 5 cases (out of 12,000 users)where someone attempted or actually gained unauthorized access to a customer's online banking account and in every case it was an ex-spouse, ex-girlfriend/ex-boyfriend, relative or roommate who was able to do it because they knew the customer's social security number and had access to the customer's paper statements.
We never had a case where a stranger hacked in and got someone's information. It was always someone the customer knew and even in those situations the people who gained unauthorized access couldn't do anything. The account numbers were masked and they couldn't transfer funds to themselves and all they managed to do was see someone else's account balance.
So I don't worry too much about doing all my financial stuff online, but I do go to a whole lot of trouble to hide all my credit cards, bank statements, checkbooks, etc. whenever I have any of my sleazy relatives come by for a visit.
Always remember that your data is unencrypted on your local system, so any spyware or virus that may be on your local system can see it when it leaves you system. At the same time, once the data travels through the SSL tunnel, it is unencrypted on the web server to which you sent your data. If that system is compromised, it can be siphoned off there as well. I'm not even going to go into problems with actually storing the data insecurely on the website or backend systems.
The problem here was simple URL manipulation which anyone with a web browser can do. Along with SQL injection and cross-site scripting, they are some of the most pervasive problems on the internet today. Literally millions of websites have these problems today. Plenty of financial institutions have had web application issues like these uncovered in the past and I would wager that plenty more problems will be uncovered in the future.
I'm not trying to "scare" anyone into not using the Internet for their financial dealings. In fact, I handle most of my finances online. But I felt that the quote, "SSL encryption is the safest way to fly" suggested that SSL was the be-all-end-all of being safe on the Internet. While SSL is important and I wouldn't log into a financial institution or submit a CC number without it, there are plenty more threats out there that the readers should consider aside from whether the little padlock appears at the bottom of their browser or not.
-Toby
http://it.slashdot.org/comments.pl?sid=230439&a...
Apparently this (or a similar) issue has been known for more than three months and not been fixed!
Low-tech vulnerability is where the most risk is, but you've got to be vigilant about everything.