IoT
5/20/2016
01:58 PM
Steve Zurier
Steve Zurier
Slideshows
Connect Directly
Twitter
RSS
E-Mail
50%
50%

5 Tips for Protecting Firmware From Attacks

Don't let hackers take advantage of holes in firmware. Here's how to stop them.
Previous
1 of 6
Next

Image Source: hackaday.com

Image Source: hackaday.com

Just about every component on a computer system contains firmware. Many people just think of the firmware on the system BIOS on a PC, but network interface cards, embedded controllers, graphics cards, USB sticks, mice, keyboards and of course, routers and switches all have firmware.

Yuriy Bulygin and John Loucaides, security researchers at Intel Security, point out that hackers attack firmware because they know many security and IT managers aren’t paying attention to it. They say security teams are so overwhelmed by the prevailing threat landscape, that they have their hands full just deploying the basics, like firewalls, intrusion prevention systems and sandboxes.

“Hackers are depending on security managers ignoring firmware, which means that spreading awareness that firmware must be protected is very important,” Loucaides says.

Bulygin and Loucaides say hackers attack firmware for three main reasons:

  • Persistence. Security mangers can clean up malware on most systems with antivirus software or sandbox it and then remediate with software. Not so with firmware. Compromised firmware could cause malware to keep coming back even after normal remediation actions. 
  • Stealth. Normal mechanisms for detecting malware do not examine firmware. Therefore, compromised firmware can be used to hide malicious behavior for a long time.
  • Full access. If malware can control system firmware, it gains full access to the system. Normal protection mechanisms used by an OS or virtual machine rely on platform characteristics that are controlled by firmware. By altering firmware, malware can usually bypass existing measures.

While much of this may be alarming, there are steps security managers can take to protect their organizations from attacks on firmware. Bulygin and Loucaides outline five tips that help security managers become aware of the issue and offer ways to take steps to plug any potential holes in firmware.

 

Steve Zurier has more than 30 years of journalism and publishing experience, most of the last 24 of which were spent covering networking and security technology. Steve is based in Columbia, Md. View Full Bio

Previous
1 of 6
Next
Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
hilalashwaq411
50%
50%
hilalashwaq411,
User Rank: Apprentice
8/27/2016 | 12:46:54 AM
Thank you
Thanks for the wonderful tips! Aside from installing anti malware software (like antivirus - ESET Antivirus etc), one's innocence of malware must be addressed. Be informed and cautious all the time.
honey143
50%
50%
honey143,
User Rank: Apprentice
5/26/2016 | 3:37:44 AM
greetings!!
Awesome article very informative..
Election Websites, Back-End Systems Most at Risk of Cyberattack in Midterms
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/14/2018
Intel Reveals New Spectre-Like Vulnerability
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/15/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-13435
PUBLISHED: 2018-08-16
** DISPUTED ** An issue was discovered in the LINE jp.naver.line application 8.8.0 for iOS. The Passcode feature allows authentication bypass via runtime manipulation that forces a certain method to disable passcode authentication. NOTE: the vendor indicates that this is not an attack of interest w...
CVE-2018-13446
PUBLISHED: 2018-08-16
** DISPUTED ** An issue was discovered in the LINE jp.naver.line application 8.8.1 for Android. The Passcode feature allows authentication bypass via runtime manipulation that forces a certain method's return value to true. In other words, an attacker could authenticate with an arbitrary passcode. ...
CVE-2018-14567
PUBLISHED: 2018-08-16
libxml2 2.9.8, if --with-lzma is used, allows remote attackers to cause a denial of service (infinite loop) via a crafted XML file that triggers LZMA_MEMLIMIT_ERROR, as demonstrated by xmllint, a different vulnerability than CVE-2015-8035 and CVE-2018-9251.
CVE-2018-15122
PUBLISHED: 2018-08-16
An issue found in Progress Telerik JustAssembly through 2018.1.323.2 and JustDecompile through 2018.2.605.0 makes it possible to execute code by decompiling a compiled .NET object (such as DLL or EXE) with an embedded resource file by clicking on the resource.
CVE-2018-11509
PUBLISHED: 2018-08-16
ASUSTOR ADM 3.1.0.RFQ3 uses the same default root:admin username and password as it does for the NAS itself for applications that are installed from the online repository. This may allow an attacker to login and upload a webshell.