![]() ![]() That’s when I learned that to open a door, sometimes you just have to knock. Their success rate was stunning and the effort they put into it was close to zero. I have seen my friends and colleagues completely break applications using seemingly random inputs. In IT we have a tendency to over-intellectualize, even when it isn’t exactly warranted. ![]() If you have tried that method, you might know that it can fail really hard-in which case your careful planning and effort goes to waste. As any good Engineer, I usually approach things using a properly construed and intelligent plan that needs to be perfectly executed with the utmost precision. I was curious if it was still possible to get credit card numbers online the way we could in 2007. But here comes the credit card hack twist. Among the contestants are phone numbers, zip-codes, and such. A lot of hits come up for this query, but very few are of actual interest. Something like: “1234 5678” (notice the space in the middle). Instead of using simple ranges, you need to apply specific formatting to your query. You can’t use the number range query hack, but it still can be done. The article’s author, again Bennett Haselton, who wrote the original article back in 2007, claims that credit card numbers can still be Googled. Yesterday, some friends of mine ( and _2501) brought a more recent Slashdot post to my attention: Credit Card Numbers Still Google-able. With a minor tweak on Haselton's old trick, I was able to Google Credit Card numbers, Social Security numbers, and any other sensitive information. After a month without a response, I notified them again to no avail. When you tried to Google a range like that, Google would serve up a page that said something along the lines of “You’re a bad person,” or more specifically, “We won’t help you hack credit cards.” By the way: here’s a full list of Issuer ID numbers.Īt the time, I didn’t think much of it, as Google immediately began to filter the types of queries that Bennett was using. For example, he could use “4060000000000000.4060999999999999” to find all the 16 digit Primary Account Numbers (PANs) from CHASE (whose cards all begin with 4060). In short, Haselton was able to find Credit Card numbers through Google, firstly by searching for a card’s first eight digits in “nnnn nnnn” format, and later using some advanced queries built on number ranges. You could imagine my surprise when I saw Bennett Haselton’s 2007 article on Slashdot: Why Are CC Numbers Still So Easy to Find?. After all, our job was to protect our users’ data, to prevent it from being hacked, stolen or misused. At this point, I’m pretty intimate with Credit Cards (CCs), Credit Card hacking and web security in general. It’s safe to say that this wasn’t a job for the faint of heart. ![]() Part of my job was to make our provider PCI-DSS compliant-that is, compliant with the Payment Card Industry – Data Security Standard. At this company, our payment provider processed transactions in the neighborhood of $500k per day. If you know me, or have read my previous post, you know that I worked for a very interesting company before joining Toptal. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |