Breach Exposes 19,000 Active US, UK Credit Cards
pnorth writes "A defunct payment gateway has exposed as many as 19,000 credit card numbers of US and UK consumers in a major worldwide breach. The data, held in Google cache, includes credit card numbers, CVVs, expiry dates, names and addresses. The credit card numbers are for accounts held with Visa, Mastercard, American Express, Solo, Switch, Delta and Maestro/Cirrus. Within the address bars of the cached pages are URLs of e-commerce sites that have become victims of the breach. They include clothing, science, health, sports and photo imaging stores. The cause appears to be a known issue with the Google search engine, in which the pages of defunct web sites containing sensitive directories remain cached and available to anyone."
It's gonna be interesting when we finally move to a cashless society. Things like this will be unforgivable in such a society. That is, we will have to have solved this problem, by and large, of card theft and purchase fraud.
I know that the card companies have been working on a method of reducing fraud by doing something like linking your card to your phone and texting you for verification when they detect suspicious activity. Or perhaps requiring you to send your picture back to them or something as a verification.
The person who can create a secondary verification system like that will make a lot of money by solving the great problem that is card-fraud.
"I Don't Have Enough Faith to be an Atheist"
It's not a problem with the idiot sites that let unprotected critical information out on a public accessible net and in addition omitted to place a well placed robots.txt, no...
IT'S GOOGLE'S FAULT!!!
Democracy is a sheep and two wolves deciding what to have for lunch. Freedom is a well armed sheep contesting the issue
How is putting all your customer's credit card information online so it is publicly available, and crawlable, Google's fault? What is the known issue? People are stupid?
The problem with slashdot is that most of its users were bullied and stuffed into lockers as kids!
This was first mentioned on Whirlpool, I was reading the thread. It appears to be deleted now however:
http://forums.whirlpool.net.au/forum-alert.cfm?a=priv-deleted&t=1165021&v=0
I.O.U One Sig.
How can you know that your card was not among those?
> The cause appears to be a known issue with the Google search engine
More like the usual issue with idiots who fail to adequately protect, secure and dispose of this sort of data in the first place. "Sensitive directories" have absolutely no business ever being readable from the web.
Company executives and IT administrators who allow this sort of security breach need to start doing hard jail time. Until this happens we'll be reading more and more of these stories by the week.
Sky subscribers are morons. They pay to be advertised at !
What, now Google is meant not to index pages which have card data on them? How exactly is that even possible?
You can bet your boots that Google Checkout is PCI DSS-compliant.
"It doesn't cost enough, and it makes too much sense."
From both the article and the summary re:
The cause appears to be a known issue with the Google search engine, in which the pages of defunct web sites containing sensitive directories remain cached and available to anyone
This makes it sound like the issue is with google's search engine and makes light of the real issue which is that at some point this information was published for all the world to see (or search engines to index) and anyone to cache (or write-down, or memorize).
Insisting on search engines removing removing this information from their indexes and remove it from their caches is just sweeping the problem under the rug : you or I taking a quick peek on the internet to see if our credit-card infomation has been published anywhere would get a false sense of security if the search engines pretended it wasn't there and that security breaches had never happened.
*tin-foil-hat-time* It seems analogous to re-writing history books to cover up prior misdeeds.
The only time I "buy" anything on the Internet is when or if the company has a 1-800 number so that I can place an order over the phone. Same with banking, which I do over the phone or at an ATM that I know. It's too easy for things to go wrong over the Internet, and too many incompetents that are running businesses (on the Internet).
Ok, by your logic all I have to do to make slashdot fail compliance is post my credit card details.
No: 5434 6625 8876 1272
CVV: 854
Exp 09/12
So how would slashdot know if that post contains valid card info or not?
Or even better, I could email this information to my competetor, then ring them and point out that they have failed compliance, as they have unsecured card information stored on their systems.
Its like if you make a credit card payment and someone videos you then a "known issue with the video camera" will allow people to see the data you entered.
That was a joke! A play on words!
Seriously though, caches are good. Worrying about credit card numbers being cached is as bad as promoting security through obscurity. We should be moving to a system that doesn't rely on "secret numbers," but instead makes use of multiple factors from the time-tested triumvirate of "something you have," "something you know," and "something you are." Something you know alone just isn't good enough for this day and age.
Google is just doing what Google does.
This game will waste your life. Don't clicky!
...why anyone would use a payment system, with no safety at all?
What I mean, is that to pay with credit cards, from what I know, you only need the data that is written right on the card. And maybe sign the payment, like you sign any contract...
Is that really how it works? Because if yes, then why in the word does anyone even consider using something like that?
I'd rather go back to bartering goods, than something like that.
When I do payments, I either do it with a bag of fixed-value credits. Like real cash in a wallet, or digital cash in a digital wallet (what we in Germany call "Geldkarte"). (Both can be filled/loaded like you fill your wallet, and when it's empty, it is empty. Additionally both are detached from the bank account. Unlike a credit card.)
Or I do it with a secure system that needs what I have, what I know, and who I am. Like a cash card. Or secure online banking with a keycard. (Both use a keyfile, that you decrypt by entering a code into a secured device with its own keyboard [and display], to create a secure channel, to transmit payment instructions, that only result in payment, if the server allows payment for that account at that moment.)
Or is it, because you have not much of a choice?
Please do not see this as a rant (it isn't one), because I really am interested in understanding this.
Any sufficiently advanced intelligence is indistinguishable from stupidity.
Cheers for the Phenom 2 :)
"It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
Cheers for the Phenom 2 :)
Happy to help, if I every find who the card belons to I will say thanks from you.
Damn you, sir! You win this round...
"It does not do to leave a live dragon out of your calculations, if you live near him." - Tolkien
And the Watergate was Washington Post's fault!
*That* is the main problem: trust and security, which turns out to be *respect* (a strong word for Japanese and other Asiatic cultures, and a weak word for "western"). Here in "western", we think in respect as up to the "is it legal?" level, while more advanced societies goes beyond that level.
ilex paraguariensis for all
What the FUCK?
There is a "defunct web site containing sensitive directories" that exposed secret information to the public for anyone to see, and now it's Google's fault that it cached that information?
Newsflash: Security that relies on "nobody knows this URL" is NOT SECURITY.
1. Yeah, that actually doesn't technically break any level of PCI DSS. You're missing at least one of two bits of information.
2. I'm sorry you missed the subtle reference to the inevitable litigation surrounding issues like this.
in order to check if you are affected or not, please reply with your card number and security code on the back of your card. [/joke]
ITNews links to a discussion threat at whirlpool.net.au which has been deleted because it is "handeled by the authorities".
And again it is a known issue of Google which reveals the deleted thread: http://209.85.229.132/search?q=cache:uf9L_DtjAzYJ:forums.whirlpool.net.au/forum-replies-archive.cfm/1165021.html+http://forums.whirlpool.net.au/forum-replies.cfm%3Ft%3D1165021&cd=1&hl=en&ct=clnk
- Martin ;-)
Well, YMMV, but from what I can read, it breaks validation types 1 to 4 at least on the no CHD storage rquirement. And the information I supplied is enough to auth a CHNP transaction.
But I think you get my point.
It seems to me that PCI DSS is this generations version of BS5750, just another excuse to create a market for over paid consultants who claim to understand the requirements.
I don't know if that was a serious question but I'm going to answer it anyway. Using regex for card numbers is childs play. Baby-play for the likes of Google.
This post contains benzene, nitrosamines, formaldehyde and hydrogen cyanide.
Comment removed based on user account deletion
Oops, you just killed a valid webpage:
http://www.merriampark.com/anatomycc.htm
*grumble* trigger-happy regexp jockeys *grumble*
"It doesn't cost enough, and it makes too much sense."
Perhaps we should revive the word "honor". At one time damaging an American's honor meant opening yourself to being murdered by duel. If you impugn my reputation or honor, your life may be forfeit. I nominate AIG executives for that. AIG versus the People in single-shot combat.
"I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
Not sure I missed some sarcasm, but I think there is a truth in your comment :-) If someone lacks respect to others, they should be accountable for that. I mean, it should suffer severe consequences instead of getting huge bonuses ;-)
ilex paraguariensis for all
remember kids now that google isnt popular its their fault if you put sensitive customer data OPENLY ON YOUR SITE.
by the same logic thumb drive makers are the blame for data loss via thumb drives.
Thank you google for giving out my CC number, luckily, I caught it fast enough...now I at least know what happened...
Isn't it more a problem with websites that allow a spider to read what should be a secure directory?
Yay me!
Credit card security is for paying equals, the people you cannot not afford to upset.
Other banks or the people data mining you.
Paying a credit card consumer breach 'fine' every so often is still cheaper than the real expense of on going consumer security.
If congress looks, any credit card company can swear they have the best security in place..
A line of top university security experts and other independent experts would tell of how the company to company transactions are secure..
Just not for you as a consumer.
Domestic spying is now "Benign Information Gathering"
That's a little oversimplified don't you think? The basis for Western society is the rule of law. While it does have some downsides it has a lot of upsides too. I wouldn't call Western society "less advanced". It's just different.
Time makes more converts than reason
the cost of setting up a new system is higher than the cost of paying for all of exploits
for the companies that is. for the individuals, your credit is destroyed, you have to spend hours cleaning up the mess, etc.
unfortunately, not enough have been victimized to make much of a ruckus. nor have the exploits been of the scale (yet) that really cost the providers dearly
but that day will come. then we will get a more secure payment system
the consumer is ignorant. the providers are content. and the tsunami is over the horizon
some huge exploit will happen in the future. and only then things will change. classic human nature: put off and ignore the inevitable because you don't want to deal with it until it is too late
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
Just out of curiosity, how was Google's Crawler allowed to FIND the information in the first place to put it in the cache?
You don't suppose that maybe the problem is in the ORIGINAL server allowing too much access, do you?
Google just "remembers" your mistake for a LONG time.
-- You can't idiot-proof anything, because they're always coming out with better idiots.
I always use single use card numbers, or generated numbers for different vendors. Although one problem I can think of is returns, I don't know how those are treated.
OpenID has instant telephone verification even for simple site logins NOW, and it works. I just enabled it the other day and tested it.
CVV numbers. Which VISA/MC tell you as a merchant you are never ever to store (it's only supposed to be sent to the payment/verification gateway in real time with the transaction).
The merchants involved should have their agreements revoked.
- Roach
I have not read the article, but it sounds like the author of this post is suggesting that google is to blame for data leaks. I think google is an effective tool for indicating data leaks. What stops someone from accessing the data if a web crawler can. I mean the crawl does not have credentials for accessing the data. That means evil people without credentials can access the data. Google just happens to cache it for latter access by evil people.
The industry could of course have a valid example CC number like using example.com as a placeholder domain.
Or just ignore the fact and rely on links to that page being in the index. One could reissue the page with all CC numbers excised (or with the first 4 numbers replaced with AAAA or whatever) and a link at the top to a page with the CC numbers still in. It wouldn't really hurt any genuine use of CC numbers it would just require a little alteration if you wanted the precise page with the CC numbners to be indexed by Google.
So some credit card numbers were stolen. So what? Nobody, except the merchants accepting them, lose anything from this. Certainly not the card holders. It is a minor hassle to get the cards reissued - and maybe the credit card company can actually take some action and do this in advance.
Is this "identity theft"? No. It certainly isn't IDENTITY THEFT!!! It is credit card fraud and it happens every day. I regularly get fraudulent charges on credit cards - using the card creates this risk. There are lots and lots of merchants out there both online and brick-and-mortar that think nothing of selling credit card numbers to thieves. It is obvious, because "stolen" credit card numbers are so incredibly common.
I am so sick of folks blaming Google Its not a FLAW in Google its a flaw in who ever left their e-buggery site insecure Google behaved as designed,It Cached and searched and archived a web page.
A possible analogy is like you make a credit card payment with a gas station and the gas station video security system records you typing in your PIN-code and doesn't handle the recording securely. Is that a known issue with the video camera (an inanimate object), or a known issue with the person that put up the security system who is too lazy to secure potentially harmful recordings?
Perhaps we can put this into a bigger question: is there a safe harbor for google to archive things accidentally put on the web forever, or are they required to do something when someone points this out something bad that their creation has done?
As a silly example, is that imagine there was a coal-burning plant built that provided electricity. Some time later it is discovered that mercury was being billowed in the air. Does the plant have the safe harbor that all it was doing was burning coal and providing electricity, both perfectly legal and standard activities and can continue to do this forever? I think not, new information about devastating side effects of their operation have been revealed. They have a duty to change their operations even though it may not have been forseen. If they do not change their operations, they can be held liable... IANAL, but this seems reasonable to me...
You'll also need an htaccess file. Otherwise you're telling any spiders who don't obey robots.txt and malicious users exactly where to go (though you shouldn't be storing credit card numbers on a web server anyway).
I sure as hell wouldn't want to try to mug a postman.
First, I've seen some of the crazy bastards outside in Winter in shorts. So they're tough as nails right there. Moreover, you could just be the unfortunate one to mug the postman that was gonna flip out at work with an uzi just as soon as he finished his shift.
Random Thoughts From A Diseased Mind (Not For Dummies)
I won't make any apologies for a two sentence post on Slashdot not being a comprehensive guide to website security. It was a simple, common example. You presented robots.txt as some kind of solution to what happened when it not only *isn't*, it could have easily made the situation much worse by pointing a big, blinking arrow to where the sensitive information is. I'm not the only person who interpreted it that way and your overreaction to it suggests you aren't as confident in your knowledge as you pretend to be.