Commonwealth EFTPOS errors Code 57
Update: The Commonwealth Bank has now responded to our inquiries. Scroll down for its response!
The blog post is a confusing read:
CBA customers can rest assured we are patched against the ‘Heartbleed’ bug.
I’ve had a few friends and customers ask me if they need to be concerned about using NetBank in light of the recent ‘Heartbleed’ OpenSSL vulnerability.
I’m happy to report that our customers can rest assured we are patched against the ‘Heartbleed’ bug and you do not need to change your NetBank password. This is a testament to the hard work of our security teams who constantly monitor and stay abreast of the latest security technologies, trends and updates.
We also offer all our NetBank customers a 100 percent security guarantee provided you keep your NetBank client number and password secure and notify us immediately of any suspicious activity on your account.
To find out more about staying safe online please visit commbank.com.au/security or take a read through my previous blogs.
Obvious errors in syntax aside, the Commonwealth Bank seems keen on ushering people along from the scene of an accident like there's nothing to see. Considering that it's the biggest breach of internet security in recent memory and a bank where most Australians transact, I'd say it is a big deal.
CommBank seems doubly keen in telling us that it knew about Heartbleed before the world did thanks to its crack team. That would be especially convenient considering that it took Google — the smartest and largest tech company on the planet — two years to find the vulnerability on its own. Even if CBA did know about it before Google did, it's pretty irresponsible not to tell people about it, no?
Regardless, CommBank won't tell people how it secured their data either in the blog post or in the comments. Right now there's a "Moderator" pissing off users by doling out the same pre-approved cookie-cutter PR response to readers who have serious questions about their money.
