Vulnerabilities / Threats
3/28/2014
12:45 PM
Connect Directly
RSS
E-Mail
100%
0%

Hackers Cash In On ATMs

Malware uses text messages and other techniques to infect ATMs and ultimately allow criminals to steal cash.

A text message is sent, and cash starts spitting out of an ATM infected with malware.

That is one of the capabilities of a sophisticated variant of malware known as Ploutus that has been linked to attacks in Mexico and the Ukraine. In the process, it has become another example of how hackers are turning their attention to ATM machines as another avenue to a bank's coffers.

"I've heard some people saying, 'Well, you know you need physical access to the machine and that makes it more difficult,' " says Symantec researcher Liam O Murchu. "And that is true, but the reason we are reporting on this is because this is something we've seen being used… So even though it may seem like, "Well, you need physical access to the machine so it's not really going to happen,' it is happening, and we're seeing people arrested in Mexico, and we're seeing it being used elsewhere."

Symantec's recent report on the capabilities of the Ploutus malware served to underscore the issue, but also drew some critics who highlighted the difficulties of getting away with opening up a machine and inserting a mobile phone, USB stick, or anything else. Yet that is precisely what researchers at the Chaos Communications Conference in December said they uncovered in the wild: attackers uploading malware onto ATMs by vandalizing machines and inserting USB sticks. They then covered up the hole so they could remain undetected.

"When I hear about a successful malware attack on any ATM, I am not particularly interested in the features which the malware implements, such as its user interface, what data it captures, how it manages the 'casher' mules, and so on," says Henry Schwarz, software projects director at ATM manufacturer Triton. "The central issue is how the malware made its way onto the ATM in the first place -- that is the attack vector which must be addressed. Once malware is running on an ATM, the damage is done."

According to Schwarz, Triton takes various precautions to prevent malware infections. For example, Triton's ATMs now verify software has been digitally signed by Triton using its private key. If the digital signature is incorrect, the ATM does not accept the software.

"The most common vulnerabilities are those that arise almost directly from making maintaining ATMs easy for technicians in the field," explains Mike Park, managing consultant at Trustwave. "These include easy-to-pick locks, the ability to bypass locks, ATM operating systems running as 'administrator' without a password, and USB ports both enabled and in the boot order before the hard drive. Many lack hard drive encryption or any form of endpoint security. Anti-virus, for instance, can bog a machine down such that transactions take far too long to complete.

"By far our most successful and easiest attacks are to gain access to the ATM network and manipulate ATM requests and responses, allowing us to gain access to the cash in the ATM without having to actually touch the machine, except to initiate a legitimate transaction."

Some of the company's most successful attacks during penetration tests do not require physical access to the device and are agnostic to the operating system, Park tells us. Network-based attacks have proven repeatedly to be both easy to exploit and lucrative, and at times testers have been able to hide the fact that the ATM was compromised from a central management application.

Based on the company's penetration tests, ATM manufacturers and banks should take measures such as adding a BIOS password, encrypting the hard drive, and installing host intrusion detection systems, Park says. In addition, armoring application binaries against reverse engineering and using endpoint security solutions can help as well.

"The biggest issue however is that implementing many of these security measures make ATM technical maintenance much more difficult, time consuming, and expensive," says Park. "Technicians will need a large ring of keys -- will need to know BIOS password and admin passwords when doing routine or emergency maintenance."

Telling ATM owners to pay more attention to physical device security in the form of cameras and other methods as opposed to upgrading devices is a losing proposition, opines Craig Young, security researcher at Tripwire.

"ATMs are networked devices which can potentially be attacked without direct physical access to the system," he says. "Migrating from [Windows] XP embedded is really the ideal solution as newer operating systems will not only benefit from ongoing security updates but also from security enhancements integrated into newer operating systems."

Support for the Windows XP embedded products varies depending on the version of the product, according to a timeline set out by Microsoft.

"From a technical standpoint, organizations not in a position to upgrade ATMs from Windows XP do have some options for system hardening," notes Young. "As a starting point, USB ports should be locked down as much as possible. This could be a physical solution such as an additional locking mechanism over the USB port or a technical solution such as disabling USB ports within software."

Attacks against ATMs are on everyone's radar, says Troy Leach, chief technology officer at PCI Security Standards Council. 

"According to findings from the ATM Industry Association’s 2012 ATM Global fraud survey, skimming remains the top global threat to ATMs, with different kinds of brute force attacks continuing unabated," he tells Dark Reading. "PIN and account data present in ATMs has become a growing target for criminals who use this stolen information to produce counterfeit cards for fraudulent transactions, primarily ATM cash withdrawals."

Brian Prince is a freelance writer for a number of IT security-focused publications. Prior to becoming a freelance reporter, he worked at eWEEK for five years covering not only security, but also a variety of other subjects in the tech industry. Before that, he worked as a ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
3/31/2014 | 5:47:36 PM
Re: Root Default of ATM
Randy, 

You bring up a good point. How come ATM's aren't secured Linux shops? I would imagine that it would be more secure and cost effective. Not to say that Linux is a cure all, just I know it has a large percentage of effective security tools and safeguards. Is it the level of support? I don't know how thorough that component would be. If someone could, please clue me in on why this hasn't come to pass?
Randy Naramore
50%
50%
Randy Naramore,
User Rank: Ninja
3/31/2014 | 11:47:11 AM
Re: Root Default of ATM
You would think that a more robust and updated OS would be used instead for ATMs of XP. XP was a great desktop system but with support being phased out and other options being available such as a locked down version of linux (take your pick) the ATMs would be less susceptable to some of the attacks than windows would be. Just a thought..
securityaffairs
50%
50%
securityaffairs,
User Rank: Ninja
3/30/2014 | 2:16:13 PM
Re: Root Default of ATM
Ryan raises an interesting issues, the security level for many ATM is not acceptable.

Banks cannot think to continue to use phase out OSs like XP while cyber threats are even more sophisticated.

Physical protection is another serious problem, why are we surprised if the computers behind ATM is easily accessible? I'm not surprised by news regarding similar hacks ... the problem is elsewhere.

Why Does BIOS of the ATM machines allow booting from external and unauthorized media (e.g. CD ROMs , USB sticks)?

What's about disk encryption to prevent disk tampering?

This hack is the result of many errors!

This is not security

Thanks

Pierluigi
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
3/28/2014 | 4:38:37 PM
Root Default of ATM
I have read a few reports about Ploutus and yes it poses a very large risk, but I think the risk lies in the machines architecture and not too much in the "malware" being transferred via the device, USB, phone, etc.

Correct me if I am mistaken but it seems that these machines are in an administrative state for routine/emergency maintenance and its only the physical barrier that truly denies access to the kingdom. But as knights circumvent a moat, people have gotten past this safeguard and are tasking the machine with minimal intrusion.

One comment I saw on a forum regarding Ploutus, though cynical, carried some truth. You can't leave a machine in root status and expect it not to perform root tasks. 

As delineated in your article, banks are now undergoing expensive counter procedures to smooth out this issue. But that is more of a reactive approach and therefore a huge security flaw. It needs to be realized that security is most effective when handled pre-emptively. For whatever reason, these machines were left in a vulnerable state with only a thin physical layer to keep people out. What are other peoples thoughts regarding the ATM "hacks"?

 
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Must Reads - September 25, 2014
Dark Reading's new Must Reads is a compendium of our best recent coverage of identity and access management. Learn about access control in the age of HTML5, how to improve authentication, why Active Directory is dead, and more.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2003-1598
Published: 2014-10-01
SQL injection vulnerability in log.header.php in WordPress 0.7 and earlier allows remote attackers to execute arbitrary SQL commands via the posts variable.

CVE-2011-4624
Published: 2014-10-01
Cross-site scripting (XSS) vulnerability in facebook.php in the GRAND FlAGallery plugin (flash-album-gallery) before 1.57 for WordPress allows remote attackers to inject arbitrary web script or HTML via the i parameter.

CVE-2012-0811
Published: 2014-10-01
Multiple SQL injection vulnerabilities in Postfix Admin (aka postfixadmin) before 2.3.5 allow remote authenticated users to execute arbitrary SQL commands via (1) the pw parameter to the pacrypt function, when mysql_encrypt is configured, or (2) unspecified vectors that are used in backup files gene...

CVE-2012-5485
Published: 2014-09-30
registerConfiglet.py in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to execute Python code via unspecified vectors, related to the admin interface.

CVE-2012-5486
Published: 2014-09-30
ZPublisher.HTTPRequest._scrubHeader in Zope 2 before 2.13.19, as used in Plone before 4.3 beta 1, allows remote attackers to inject arbitrary HTTP headers via a linefeed (LF) character.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Chris Hadnagy, who hosts the annual Social Engineering Capture the Flag Contest at DEF CON, will discuss the latest trends attackers are using.