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.

Endpoint Security

8/26/2019
06:03 PM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

NSA to Share Added Security for Firmware Functions

Most people think of the National Security Agency as the home of operational intelligence gathering. But many people are unaware of the research that it has done and released to the public.

Most people think of the National Security Agency as the home of operational intelligence gathering. But many people are unaware of the research that it has done and released to the public. The Security Enhanced Linux module is one older but still quite viable example. Ghidra is a malware reverse-engineering open source tool, that was released as open source by the NSA at this year's RSA conference.

Now, NSA is looking at firmware. Firmware has become an attractive target for attackers since it can slip around most defensive measures. ESET found a UEFI rootkit in the wild for the first time last year.

Also, firmware has to run in an extremely privileged mode to do its functions, which means it may have access to everything in the computer.

Ghidra is being used by the Coreboot open source project as one of its central elements in securing firmware. Ghidra modules will allow loading PCI option ROMs into Ghidra along with firmware images and scripts to aide in the UEFI binary reverse engineering.

Eugene Myers, who works in the National Security Agency's Laboratory for Advanced Cybersecurity, is developing firmware hardening that will show up In the Coreboot project. He will be heading up the SMI Transfer Monitor with protected execution (STM-PE) project that will work with x86 processors that run Coreboot.

The STM is a hypervisor, so it can isolate physical hardware from a computer's operating system.

The STM takes the operating code and puts it in a "box" so it can only access the device system that it needs. It lives inside the System Management Mode, which is a "ring -2" isolated environment offering protected execution against tampering of low-level services. The low-level services might include power management, security functions, calls to the Trusted Platform Module and the like. This particular approach has been under development for the last seven years. Myers wrote a paper in 2018 describing the work that had been done on the Intel x86. Intel released the STM specification and documentation of the SMT firmware security feature as open source in 2015.

The idea of using the open source mechanism should serve as a way for anyone to verify that there is no backdoor in there put in by the NSA. That is, if the examiner is qualified and competent to do so. The NSA has previously snuck in computation methods (like doctored ECC curves) inside some released work which contained backdoors that were known to it. Therefore, they would be at an advantage dealing with any adversary that used their released work for everyday use. Myers may have dealt with that objection by finding a way for anyone to build out their own STM and not use the NSA version, even Linux users. That Linux version is now up on GitHub.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-20491
PUBLISHED: 2021-04-16
IBM Spectrum Protect Server 7.1 and 8.1 is subject to a stack-based buffer overflow caused by improper bounds checking during the parsing of commands. By issuing such a command with an improper parameter, an authorized administrator could overflow a buffer and cause the server to crash. IBM X-Force ...
CVE-2021-22539
PUBLISHED: 2021-04-16
An attacker can place a crafted JSON config file into the project folder pointing to a custom executable. VScode-bazel allows the workspace path to lint *.bzl files to be set via this config file. As such the attacker is able to execute any executable on the system through vscode-bazel. We recommend...
CVE-2021-31414
PUBLISHED: 2021-04-16
The unofficial vscode-rpm-spec extension before 0.3.2 for Visual Studio Code allows remote code execution via a crafted workspace configuration.
CVE-2021-26073
PUBLISHED: 2021-04-16
Broken Authentication in Atlassian Connect Express (ACE) from version 3.0.2 before version 6.6.0: Atlassian Connect Express is a Node.js package for building Atlassian Connect apps. Authentication between Atlassian products and the Atlassian Connect Express app occurs with a server-to-server JWT or ...
CVE-2021-26074
PUBLISHED: 2021-04-16
Broken Authentication in Atlassian Connect Spring Boot (ACSB) from version 1.1.0 before version 2.1.3: Atlassian Connect Spring Boot is a Java Spring Boot package for building Atlassian Connect apps. Authentication between Atlassian products and the Atlassian Connect Spring Boot app occurs with a se...