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.

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
Oldest First  |  Newest First  |  Threaded View
honey143
50%
50%
honey143,
User Rank: Apprentice
5/26/2016 | 3:37:44 AM
greetings!!
Awesome article very informative..
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.
Florida Town Pays $600K to Ransomware Operators
Curtis Franklin Jr., Senior Editor at Dark Reading,  6/20/2019
Pledges to Not Pay Ransomware Hit Reality
Robert Lemos, Contributing Writer,  6/21/2019
AWS CISO Talks Risk Reduction, Development, Recruitment
Kelly Sheridan, Staff Editor, Dark Reading,  6/25/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Building and Managing an IT Security Operations Program
As cyber threats grow, many organizations are building security operations centers (SOCs) to improve their defenses. In this Tech Digest you will learn tips on how to get the most out of a SOC in your organization - and what to do if you can't afford to build one.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-10133
PUBLISHED: 2019-06-26
A flaw was found in Moodle before 3.7, 3.6.4, 3.5.6, 3.4.9 and 3.1.18. The form to upload cohorts contained a redirect field, which was not restricted to internal URLs.
CVE-2019-10134
PUBLISHED: 2019-06-26
A flaw was found in Moodle before 3.7, 3.6.4, 3.5.6, 3.4.9 and 3.1.18. The size of users' private file uploads via email were not correctly checked, so their quota allowance could be exceeded.
CVE-2019-10154
PUBLISHED: 2019-06-26
A flaw was found in Moodle before versions 3.7, 3.6.4. A web service fetching messages was not restricted to the current user's conversations.
CVE-2019-9039
PUBLISHED: 2019-06-26
The Couchbase Sync Gateway 2.1.2 in combination with a Couchbase Server is affected by a previously undisclosed N1QL-injection vulnerability in the REST API. An attacker with access to the public REST API can insert additional N1QL statements through the parameters ?startkey? and ?endkey? of the ?_a...
CVE-2018-20846
PUBLISHED: 2019-06-26
Out-of-bounds accesses in the functions pi_next_lrcp, pi_next_rlcp, pi_next_rpcl, pi_next_pcrl, pi_next_rpcl, and pi_next_cprl in openmj2/pi.c in OpenJPEG through 2.3.0 allow remote attackers to cause a denial of service (application crash).