Risk
8/24/2012
11:51 AM
50%
50%

Safer Boots: Feds Urge Malware-Resistant BIOS

NIST advises PC and server makers strengthen the security of BIOS ROM chip flashware. Attacks against BIOS can be used to create persistent rootkits that survive reboots.

11 Security Sights Seen Only At Black Hat
11 Security Sights Seen Only At Black Hat
(click image for larger view and for slideshow)
Memo to manufacturers: Improve the security of the BIOS ROM chip flashware running on PCs and servers.

That's the gist of a recently released draft report from the National Institute of Standards and Technology (NIST), which offers advice on how manufacturers can better protect the BIOS flashware used on servers. NIST currently is soliciting comments on the draft report, which can be filed with the agency until Sept. 14, 2012.

Why worry about the BIOS? "Unauthorized modification of BIOS firmware by malicious software constitutes a significant threat because of the BIOS's unique and privileged position within the PC architecture. Malicious BIOS modification could be part of a sophisticated, targeted attack on an organization--either a permanent denial of service or a persistent malware presence," says the report.

Previous examples of BIOS-infecting malware are relatively rare, but include the Windows-targeting CIH or Chernobyl virus, which appeared in 1998 and could flash a BIOS and corrupt it, after erasing the data on a PC.

[ Leave hacker payback to the experts: Strike Back At Hackers? Get A Lawyer. ]

But worries over BIOS security have been growing, especially since researchers in 2009 demonstrated a technique for injecting code into any unsigned firmware. Last year, security researchers discovered a BIOS-altering rootkit called Mebromi, which can alter boot-time instructions in the BIOS, which in turn alter the computer's master boot record (MBR). When the PC powers on, firmware in the BIOS ROM loads and executes the MBR, which is the sector at the very beginning of a hard drive, and thus the first to load.

Infecting the BIOS and MBR makes it difficult for antivirus software to find or eradicate the malware, raising the possibility that attackers could create boot-proof and antivirus-resistant rootkits.

"Developing an antivirus utility able to clean the BIOS code is a challenge, because it needs to be totally error-proof, to avoid rendering the system unbootable at all," said Webroot security researcher Marco Giuliani last year, in his analysis of Mebroni. In fact, even small coding errors made when trying to repair a BIOS could brick the machine. On the upside, however, in the case of Mebroni, the malware could only infect PCs with a BIOS ROM made by Award, which is part of Phoenix.

As Mebroni demonstrates, servers aren't the only systems at risk from a BIOS attack. Last year, NIST released "BIOS Protection Guidelines" for PC manufacturers, to help them prevent unwanted BIOS modification on PCs by attackers.

The report warned that BIOS implementations could become more susceptible to such attacks in the future. "The move from conventional BIOS implementations to implementations based on the Unified Extensible Firmware Interface (UEFI) may make it easier for malware to target the BIOS in a widespread fashion, as these BIOS implementations are based on a common specification," it said, meaning that attackers could potentially hit more targets at once with a single piece of malware.

Accordingly, NIST recommends that manufacturers begin cryptographically signing their BIOS updates, and treating the BIOS as an essential part of PC security. "By building security into the firmware, you establish the foundation for a secure system," report co-author Andrew Regenscheid told ScienceDaily.

Mobile employees' data and apps need protecting. Here are 10 ways to get the job done. Also in the new, all-digital 10 Steps To E-Commerce Security special issue of Dark Reading: Mobile technology is forcing businesses to rethink the fundamentals of how their networks work. (Free registration required.)

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-7421
Published: 2015-03-02
The Crypto API in the Linux kernel before 3.18.5 allows local users to load arbitrary kernel modules via a bind system call for an AF_ALG socket with a module name in the salg_name field, a different vulnerability than CVE-2014-9644.

CVE-2014-8160
Published: 2015-03-02
net/netfilter/nf_conntrack_proto_generic.c in the Linux kernel before 3.18 generates incorrect conntrack entries during handling of certain iptables rule sets for the SCTP, DCCP, GRE, and UDP-Lite protocols, which allows remote attackers to bypass intended access restrictions via packets with disall...

CVE-2014-9644
Published: 2015-03-02
The Crypto API in the Linux kernel before 3.18.5 allows local users to load arbitrary kernel modules via a bind system call for an AF_ALG socket with a parenthesized module template expression in the salg_name field, as demonstrated by the vfat(aes) expression, a different vulnerability than CVE-201...

CVE-2015-0239
Published: 2015-03-02
The em_sysenter function in arch/x86/kvm/emulate.c in the Linux kernel before 3.18.5, when the guest OS lacks SYSENTER MSR initialization, allows guest OS users to gain guest OS privileges or cause a denial of service (guest OS crash) by triggering use of a 16-bit code segment for emulation of a SYS...

CVE-2014-8921
Published: 2015-03-01
The IBM Notes Traveler Companion application 1.0 and 1.1 before 201411010515 for Window Phone, as distributed in IBM Notes Traveler 9.0.1, does not properly restrict the number of executions of the automatic configuration option, which makes it easier for remote attackers to capture credentials by c...

Dark Reading Radio
Archived Dark Reading Radio
How can security professionals better engage with their peers, both in person and online? In this Dark Reading Radio show, we will talk to leaders at some of the security industry’s professional organizations about how security pros can get more involved – with their colleagues in the same industry, with their peers in other industries, and with the IT security community as a whole.