Vulnerabilities / Threats
11/17/2010
03:54 PM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%
Repost This

Possible New Threat: Malware That Targets Hardware

Researchers demonstrate proof-of-concept for developing malware that attacks specific hardware processors with 'surgical' precision

French researchers say it's possible to write malware that attacks specific hardware processors rather than operating systems or applications.

Anthony Desnos, Robert Erra, and Eric Filiol, of Ecole Suprieure d'Informatique Electronique Automatique (ESIEA) in Paris, have developed a proof-of-concept for hardware-specific malware, which they consider a step up from Stuxnet and a potentially key weapon in cyberwarfare. The malware can easily identify and target specific hardware systems based on the on-board processor chip, the researchers say.

They used the so-called floating point arithmetic (FPA) to help identify processors, including AMD, Intel Dual-Core and Atom, SPARC, Digital Alpha, Cell, and Atom. Hardware malware doesn't exploit vulnerabilities in hardware -- it preys on actual features: "We just exploit differences in processor features. There will be always such differences," Filiol says.

In order to pinpoint the type of processor, the malware would see how a processor handles certain mathematical calculations. This breed of malware is not any more difficult to create than malware that targets software vulnerabilities, Filiol says. "The malware algorithm is the same. You just have to know which processor-specific information to use to trigger the attack," he says. The tricky part is that information is often a closely held secret, he says.

The researchers maintain that targeted attacks like Stuxnet are a major threat, but it's not always so simple for the attacker to be sure what software is running on a targeted machine. "While it can be very difficult to forecast and envisage which kind of applications is likely to be present on the target system (it can be a secret information), the variety in terms of hardware -- and especially as far as processors are concerned -- is far more reduced due to the very limited number of hardware manufacturers," the researchers wrote in their paper on the malware research.

Hardware malware gives cyberwarfare another weapon. "You can arrange things in such a way that effectively Iran buys a set of computers with Intel processor of a given type and family. Then you can strike them selectively -- and only these computers -- whatever Iran has installed on those computers, [whether it's] Linux, Windows, or any application," Filiol says.

Marc Maiffret, chief technology officer at eEye Digital Security, says he doesn't see hardware malware posing a major threat anytime soon. "While it is interesting to perform this sort of processor fingerprinting, malware will still need to look at other factors to make sure it is hitting the right target, as there is plenty of overlap in systems and what processors they use," Maiffret says. "To put it another way, I think we will continue to see targeting happening more in the way that Stuxnet did it than via processor fingerprinting."

Filiol, meanwhile, says he and his colleagues decided to publish part of their research to raise awareness about this threat. "Even rogue countries and bad guys are doing research. So attacks using those techniques can strike our own countries. That is why we have decided to publish part of our research: to make people aware of the threat," he says.

The malware could be used to wage Distributed Denial-of-Service (DDoS) and any other attack software malware can execute. The idea is for "far more precise and targeted attacks, at a finer level (surgical strikes) in a large network of heterogeneous machines but with generic malware," the research paper says.

There's no way for a processor manufacturer to mitigate such a targeted attack by "patching," either, "unless manufacturers would accept to use the same computation techniques and the same processor designs," he says. But that's obviously not a realistic option, he says.

A full copy of the research is available here (PDF) for download.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.

Kelly Jackson Higgins is Senior Editor at DarkReading.com. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise Magazine, ... View Full Bio

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2012-0360
Published: 2014-04-23
Memory leak in Cisco IOS before 15.1(1)SY, when IKEv2 debugging is enabled, allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCtn22376.

CVE-2012-1317
Published: 2014-04-23
The multicast implementation in Cisco IOS before 15.1(1)SY allows remote attackers to cause a denial of service (Route Processor crash) by sending packets at a high rate, aka Bug ID CSCts37717.

CVE-2012-1366
Published: 2014-04-23
Cisco IOS before 15.1(1)SY on ASR 1000 devices, when Multicast Listener Discovery (MLD) tracking is enabled for IPv6, allows remote attackers to cause a denial of service (device reload) via crafted MLD packets, aka Bug ID CSCtz28544.

CVE-2012-3062
Published: 2014-04-23
Cisco IOS before 15.1(1)SY, when Multicast Listener Discovery (MLD) snooping is enabled, allows remote attackers to cause a denial of service (CPU consumption or device crash) via MLD packets on a network that contains many IPv6 hosts, aka Bug ID CSCtr88193.

CVE-2012-3918
Published: 2014-04-23
Cisco IOS before 15.3(1)T on Cisco 2900 devices, when a VWIC2-2MFT-T1/E1 card is configured for TDM/HDLC mode, allows remote attackers to cause a denial of service (serial-interface outage) via certain Frame Relay traffic, aka Bug ID CSCub13317.

Best of the Web