News for hackers. Stuff that matters.
Re:Why blurring sensitive information is a bad idea by InclinedPlane on Thursday November 25, 2010 @03:09AM (#1939699)
Bank of America uses a horrible method for generating debit card numbers. It's a standard prefix + account number + sequence number + check digit. If you have stolen someone's BofA debit card number then you can easily guess the replacement card's number (just increment the sequence number and recalculate the check digit). From there you just need to guess the expiration date (a comparatively trivial task).
Re:Why blurring sensitive information is a bad idea by ig1 on Thursday November 25, 2010 @08:21AM (#1940177)
Also they generate your PIN by running your account number through a DES encryption round. This method is known to be vulnerable to attack:

http://www.cl.cam.ac.uk/~mkb23/research/PIN-Cracking.pdf

Re:Why blurring sensitive information is a bad idea by wdewind on Thursday November 25, 2010 @06:18PM (#1941226)
Chase PINs are by default 3210 - guess how many people still have that pin.
Re:Why blurring sensitive information is a bad idea by ubernostrum on Thursday November 25, 2010 @03:56AM (#1939761)
Either you're skipping over a lot of information in the process of how that number's generated, or that's not how they do it anymore (and not how they've done it for at least the last couple of years).
Re:Why blurring sensitive information is a bad idea by blasdel on Thursday November 25, 2010 @08:57AM (#1940229)
I got a replacement BofA debit card a few months ago, and this is exactly how they did it — only the last two digits are different.

This may be only in Washington and Idaho though, as there are several different legacy BofA backends as a result of M&A bullshit.

Re:Why blurring sensitive information is a bad idea by nodata on Thursday November 25, 2010 @03:52AM (#1939758)
But that's for debit cards - I think most banks include the account number in a debit card number. You would still need the CCV number from the back of the card for the attack to work.
Re:Why blurring sensitive information is a bad idea by InclinedPlane on Thursday November 25, 2010 @04:26AM (#1939812)
I haven't noticed any other bank which had the same practice.

Also, not all online merchants use CCV. Also consider the risk of creating fake physical CCs, no address or CCV necessary.

Re:Why blurring sensitive information is a bad idea by Cushman on Thursday November 25, 2010 @06:38AM (#1939991)
Just checked— my credit union debit card number includes my account number.
Re:Why blurring sensitive information is a bad idea by hboon on Thursday November 25, 2010 @04:17AM (#1939798)
CCVs aren't always required for transactions.
Re:Why blurring sensitive information is a bad idea by lwhi on Thursday November 25, 2010 @06:35AM (#1939985)
CCV proves the cardholder was present at the time of the transaction. Online merchants are never allowed to store CCV numbers.
Re:Why blurring sensitive information is a bad idea by dedward on Thursday November 25, 2010 @10:03AM (#1940344)
edit: CCV proves that you at one time had access to the CCV number.

Online merchants are supposed to comply with PCI-DSS - not store your CCV ever, never transmit your number unencrypted, never store cardholder information unencrypted, plus tons of management controls and audit controls over the same.

In practice, let's just say lazy programming is everywhere. I've seen many people who handle online transactions and violate PCI-DSS to some degree, including storing CCV numbers.

Re:Why blurring sensitive information is a bad idea by nodata on Thursday November 25, 2010 @06:54AM (#1940025)
They can ask for them though.
Re:Why blurring sensitive information is a bad idea by lwhi on Thursday November 25, 2010 @07:44AM (#1940112)
.. indeed, and they often do.