POS Vendor Uses Same Short, Numeric Password Non-Stop Since 1990
mask.of.sanity writes: Fraud fighters David Byrne and Charles Henderson say one of the world's largest Point of Sale systems vendors has been slapping the same default passwords – 166816 – on its kit since 1990. Worse still: about 90 per cent of customers are still using the password. Fraudsters would need physical access to the PoS in question to exploit it by opening a panel using a paperclip. But such physical PoS attacks are not uncommon and are child's play for malicious staff. Criminals won't pause before popping and unlocking. The enraged pair badged the unnamed PoS vendor by its other acronym labelling it 'Piece of S***t.
The fact that the vendor did not use a strong password does not make the system a "piece of shit." It just means that the vendor did not use a strong default password.
the 10% who managed to change the default password replaced it by 12345
If they don't name the vender then what will change?
How can users be warned?
How do we know its even true?
They might as well be bashing some made up system by some fake company that doesn't exist.
I have to return some videotapes...
What could someone possibly do if they gain admin access to a POS? Is this a Windows CE system where someone could run arbitrary code? Or is this a bespoke system where the admin password just gives you access to the settings of the system? The article mentions staff using a POS server to play games and download porn on but that is a server probably running Windows Server with some POS server software from the vendor. Rather than just making fun of the name, these guys should explain what exactly does the admin password get you.
Getting access to the network is something different. You could update every POS terminal out there with your own code to steal CCs or crash every terminal on Black Friday.
166831 has been the default pw on VeriFone card terminals and "multilane" on Hypercom ones for as long as I can remember. Of course these are supposed to be changed at install time, but we know how that goes...
The pair iterated some brazen criminal and hopeless customer cases they each dealt with while at Trustwave where PoS systems had been compromised. ...
In another, forensics were left stumped by a carder's keylogger which had logged repeat keys (such as aaaaa ggggg bbbbb) entered on the PoS server. It was later revealed staff had used the machine to play Guitar Hero, Call of Duty, and download porn.
Forensics had even established which songs were played based on the logged keys.
The researchers found that next to the ubiquitous use of the password 166816 amongst separate manufacturers, that Deep Purple's "Smoke on the Water" was the most played song on compromised PoS terminals. Strange.
The vendor recently updated the default password to "166832".
I am very small, utmostly microscopic.
Which is why vendors shouldn't ship products with default passwords at all. Instead, they should require all users to set a password when the system is first installed.
And the customer will simply set it to "123456".
I had a client in the financial business, and the so-called, "Office-Manager" / Comptroller set all the passwords to "password" and several variations on this! He REFUSED to set them to secure passwords, even though if they were hacked, they could have lost millions of dollars in their client's money and securities!
That company is now someone else's headache now.
And the customer will simply set it to....
Than the onus of responsibility lies with the client of the vendor and not with the PoS vendor directly. Yes, the PoS vendor could enforce password complexity because it's industry best practice to do so, but not required unless legislated into law.
Life is not for the lazy.
You'll need a three day wait and a background check to secure one of these terrorist "paperclips". Sure, you could 3D bend your own with some wire and a few thousand dollars in equipment, but it will still be inferior to the real thing.
-SD
âoeWho knew something as harmless as willful ignorance could end up having real consequences?â
Ok, how about the fact that credit card numbers are stored in the memory dump of the unit? When encrypted, credit cards storage uses a symmetric key? Servers are regularly stolen, but the drives are not encrypted? The software must be installed as the admin user?
From a security perspective, these units really are a POS and a betrayal of trust by the vendors. Most retailers do not have staff on-property to do IT security, so they out-source it. They have been charged an arm and a leg, but do not get a secure, reliable system.
Our solution by Food Service Solutions has a hard-coded superuser admin account with the username of "a" and the password of "a."
It's used by thousands of institutions.
You can't disable it.
I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
What if you made the default password the date the system was turned on? Sure, it's a simple 8 digit numeric value, but it would be somewhat unique per machine or local bank of machines. Don't ask them for a default password, tell them what it is and make them go change it. Various studies suggest they probably won't.
Any half-decent system will disallow passwords like this.
Enforce strong passwords? Prepare for a sticky notes.