- 10 Hot Big Data Startups to Watch
- 11 Unique Uses for Google Glass, Demonstrated by Celebs
- How to Export Your Google Reader Account
- How to Better Engage Millennials (and Why They Aren't Really so Different)
IDG News Service - Security researcher Jesse D'Aguanno has developed what he bills as the first Trojan horse malware for Research in Motion's (RIM's) BlackBerry e-mail device.
The software, which was demonstrated at the Defcon hacker conference over the weekend, appears to be a free tic-tac-toe download. Once downloaded, however, it works with another piece of code, called BBProxy, that can be used to attack vulnerable machines within the corporate network.
D'Aguanno plans to make the BBProxy software, but not the Trojan horse code, available on his company's Web site within the next few days. It will be available here.
The BlackBerry hack was written to show that while these devices are often not treated with the same concern as PCs, they can be equally dangerous, said D'Aguanno, director of professional services and research with Praetorian Global.
When users think of the BlackBerry's security, they are too focused on protecting the device's data, and tend to ignore its networking capabilities. D'Aguanno said. "It's a computer that has constant access to your internal network."
After reviewing his research, RIM published two documents describing how to configure BlackBerry Enterprise Servers so they are not vulnerable to this attack, D'Aguanno said.
RIM said that attacks such as D'Aguanno's were possible on any mobile device and that they could be avoided by properly configuring the BlackBerry Enterprise Server.
"The IT policy settings for preventing malware exploits are built into the BlackBerry Enterprise Server software and can be set by the administrator," RIM said in a statement. RIM's white papers on the subject can be found here.
One security expert agreed that users tend to overlook the capabilities of machines such as the BlackBerry.
"When people install these types of devices they are very casual about the policy around the device," said Paul Henry, vice president of strategic accounts with Secure Computing. "There's the assumption that because they're encrypted, they have to be secure."
"It all points to a much bigger problem," he said. "For whatever reason, as soon as a device is put into the marketplace with encryption being used, everybody forgets about the endpoints."