Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

11/17/2010
03:54 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

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 the Executive Editor of Dark Reading. 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 ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
NSA Appoints Rob Joyce as Cyber Director
Dark Reading Staff 1/15/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: I like the old version of Google assistant much better.
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-8567
PUBLISHED: 2021-01-21
Kubernetes Secrets Store CSI Driver Vault Plugin prior to v0.0.6, Azure Plugin prior to v0.0.10, and GCP Plugin prior to v0.2.0 allow an attacker who can create specially-crafted SecretProviderClass objects to write to arbitrary file paths on the host filesystem, including /var/lib/kubelet/pods.
CVE-2020-8568
PUBLISHED: 2021-01-21
Kubernetes Secrets Store CSI Driver versions v0.0.15 and v0.0.16 allow an attacker who can modify a SecretProviderClassPodStatus/Status resource the ability to write content to the host filesystem and sync file contents to Kubernetes Secrets. This includes paths under var/lib/kubelet/pods that conta...
CVE-2020-8569
PUBLISHED: 2021-01-21
Kubernetes CSI snapshot-controller prior to v2.1.3 and v3.0.2 could panic when processing a VolumeSnapshot custom resource when: - The VolumeSnapshot referenced a non-existing PersistentVolumeClaim and the VolumeSnapshot did not reference any VolumeSnapshotClass. - The snapshot-controller crashes, ...
CVE-2020-8570
PUBLISHED: 2021-01-21
Kubernetes Java client libraries in version 10.0.0 and versions prior to 9.0.1 allow writes to paths outside of the current directory when copying multiple files from a remote pod which sends a maliciously crafted archive. This can potentially overwrite any files on the system of the process executi...
CVE-2020-8554
PUBLISHED: 2021-01-21
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.externalIPs field, to intercept traffic to that IP address. Additionally, an attacker who is able to patch the status (which is considered a privileged operation and should not typicall...