The modified application was Trojan.ibank, which was recently found to be trolling for SAP installations by researchers at Dr. WEB, says Alexander Polyakov, co-founder and CTO of ERPScan. Polyakov brought up the modified malware in a broader talk at RSA about the dangers of SAP and ERP vulnerabilities. Polyakov told Dark Reading that one of the likely ways attackers could be using such targeted, malicious functionality could be for the purpose of gathering information that could be sold to third parties on the black market. But there could be another more dangerous motive.
[How do you know if you've been breached? See Top 15 Indicators of Compromise.]
"A second way to use it ... is to wait until a critical mass of systems are infected and then upload a special module for SAP," he says, explaining this could be disastrous when combined with ibank's password-stealing functionality. "There are dozens of ways to steal those passwords and use them. It is possible to connect to SAP Server and do any kind of fraud in the system, or simply steal critical information, such as client lists or employees' personal information. We decided to warn people and SAP's Security response team with whom we closely work before this can happen."
A long-time advocate for the improvement of security in business-critical business applications, such as SAP, Polyakov last week also presented findings from a recent survey of common SAP vulnerabilities and misconfigurations found within the typical enterprise. One of the key findings revolved around lingering problems from an extremely critical heap overflow vulnerability that ERPScan discovered and for which it was nominated for a Pwnie award at Black Hat Vegas.
"The vulnerability allows attackers to get full control of an SAP router within one TCP packet and thus obtain access to the internal network of a company," he says. "This issue was closed in May, but after almost half-a-year we found that only 15 percent from about 5,000 SAP routers available on the Internet were patched."
According to Polyakov, while business-critical application vulnerabilities have received more attention in the past few years, enterprises still have a lot of work ahead of them. He says that systems are "way easier" to break than browsers or operating systems, and yet they are at the heart of most business processes and could make or break the viability of the business. For example, Polyakov points to an attack against Istanbul Provincial Administration, where hackers were essentially able to erase debts by breaking into a business-critical application.
"But if we talk about espionage, it's hard to find many public examples mostly because only 10 percent of SAP systems that we analyzed use logging, which means that even if there is a breach, it's almost impossible to find it," he says. "As for the unpublished attacks, some customers told us about internal fraud, like salary modification or backdoors, left in ABAP code by third-party developers."
As enterprises endeavor to lock down these applications, Polyakov encourages them to follow the work his firm is doing on www.EAS-SEC.org, which he says will provide a framework for securing implementation, maintenance, and development of custom applications.
"It's kind of OWASP for Business applications, but slightly different," he says. "This framework can help you to find most critical issues at first, and then go to less important."
Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.