Microsoft Attack Surface Analyzer 2.0: for Windows/Mac/Linux

https://www.microsoft.com/security/blog/2019/05/15/announcing-new-attack-surface-analyzer-2-0/

https://github.com/Microsoft/AttackSurfaceAnalyzer

[…]Attack Surface Analyzer 2.0 now runs on Windows, Linux, and macOS and is available as an open source project on GitHub. Attack Surface Analyzer 2.0 can help you identify potential security risks introduced by changes to an operating system’s security configuration by identifying changes in key areas, including: File System, User Accounts, System Services, Network Ports (listeners), System Certificate Stores, Windows Registry[…]

The Hacker’s hardware Toolkit

“The best hacker’s gadgets for Red Team pentesters and security researchers.”

https://github.com/yadox666/The-Hackers-Hardware-Toolkit

FishMinder: Redfish Event Receiver

A new Redfish tool:

This project provides a daemon that can be used to retrieve events from a Redfish Event Service. The DMTF Redfish standard defines a service that a client can post subscription requests to. Such request would outline what type of events the client is interested in. In the Fishminder project we only subscribe to events of the type Alert. The client would also need to tell the Event Service where to send the events. The Event Service sends events to the clients through a RESTful POST operation. Therefore the Fishminder daemon is hosting a REST server that can accept such events and places them in a Sqlite database (the table name is “events”).

https://github.com/fishminder/fishminder

Alt text

Uefi-Ext2-Reader: UEFI file system driver for Linux Ext2

There’s another Linux ext2 file system for UEFI being worked on:

Uefi-Ext2-Reader: This is a project for System Software subject for my study in Gdansk University of Technology. UEFI supports only Windows FAT file system. I implemented a protocol that allows to read files from Linux Ext2 partition in UEFI. I used VisualUEFI (https://github.com/ionescu007/VisualUefi.git) for compiling process.

https://github.com/RutEK46/Uefi-Ext2-Reader

Intel® FSP External Architecture Specification v2.1 Has Been Released

Nate DeSimone announced the availability of the FSP 2.1 spec.

We are pleased to announce that the FSP External Architecture Specification v2.1 has been posted to https://www.intel.com/fsp!

AmberLakeFspBinPkg has been released on https://github.com/IntelFsp/FSP, which provides the first implementation of FSP 2.1. This FSP is backward compatible with Kaby Lake, so there should be a good amount of existing hardware available for those who are interested in trying FSP 2.1. Looking forward, our upcoming Ice Lake and Comet Lake platforms will have FSP 2.1 binaries once they are released.

MinPlatform and FSP 2.1 provide a complete and native UEFI firmware implementation and together they are Intel’s preferred method of implementing open source UEFI firmware today. We will be pushing patches to the mailing list that add FSP 2.1 dispatch mode support to KabyLakeOpenBoardPkg in edk2-platforms soon!

For more info, see the full post on the edk2.groups.io mailing list archives.

https://edk2.groups.io/g/announce/message/18

New ACPI tables for 2018 and 2019

Re: https://firmwaresecurity.com/2017/11/21/new-acpi-ids-for-november-nexstgo-and-insyde/ and https://firmwaresecurity.com/2017/05/31/new-acpi-registry-updates-for-2017/

Here are the new ACPI entries for 2019 (so far):
1) Amazon Corporation, AMZN, 02/06/2019, https://www.amazon.com/
2) ASEM S.p.A., ASEM, 04/29/2019,
http://www.asem.it/
3) Guizhou Huaxintong Semiconductor Technology Co., Ltd, HXTS, 01/18/2019
, http://www.hxt-semitech.com/

New ACPI entries for 2018:
1) Ampere Computing, AMPC, 03/29/2018, https://amperecomputing.com/
2) COMHEAR, INC., CMHR, 08/02/2018,
https://www.comhear.com/
3) DMIST RESEARCH LTD, DMST, 07/09/2018,
http://www.dmist.com/
4) G2touch Co., LTD, GTCH, 12/04/2018,
http://www.g2touch.co.kr/
5) IDEMIA, IDEM, 06/26/2018,
https://www.idemia.com/
6) Sensel, Inc., SNSL, 08/20/2018,
https://sensel.com/
7) Vishay Intertechnology, Inc., VSHY, 07/09/2018
, https://www.vishay.com/

More info:
https://uefi.org/acpi_id_list
https://uefi.org/acpi
https://uefi.org/PNP_ACPI_Registry
https://uefi.org/uefi-acpi-export

Fortinet: How to Cost-Effectively Dynamically Analyze UEFI Malware

By Minh Tran | May 14, 2019

A FortiGuard Labs How-To Guide for Cybersecurity Threat Researchers

Unified Extensible Firmware Interface (UEFI) is a specification that defines an interface between platform firmware and an OS. In a nutshell, UEFI replaces the BIOS in previous systems. Since UEFI is required for Secure Boot (ever since the Windows 8 operating system released in 2012), virtually all modern PCs come with UEFI firmware. Naturally, with the growing popularity of UEFI systems, and the fact that UEFI firmwares have even higher privilege than the OS/ hypervisor, adversaries are starting to focus on exploiting this new attack surface. This is evidenced by the UEFI rootkit found recently from the Sednit group.Consequently, there is a pressing need for security researchers to be able to handle this novel threat. In this blog post, we will show you how.

https://www.fortinet.com/blog/threat-research/how-to-cost-effectively-dynamically-analyze-uefi-malware.html

ZombieLoadAttack.com, CPU.fail, MDSattacks.com…

Busy day for news…

https://software.intel.com/security-software-guidance/insights/deep-dive-intel-analysis-microarchitectural-data-sampling

https://mdsattacks.com/

https://cpu.fail/

https://zombieloadattack.com/

11 new security advisories from Intel today

The MDS stuff will get all the press, but there are UEFI, ME, AMT and other advisories…

INTEL-SA-00252
Intel® Driver & Support Assistant Advisory
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00252.html

INTEL-SA-00251
Intel® NUC Advisory
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00251.html

INTEL-SA-00249
Intel® i915 Graphics for Linux Advisory
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00249.html

INTEL-SA-00245
Intel Unite® Client for Android* Advisory
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00245.html

INTEL-SA-00244
Intel® Quartus® Software Advisory
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00244.html

INTEL-SA-00234
Intel® SCS Discovery Utility and Intel® ACU Wizard Advisory
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00234.html

INTEL-SA-00233
Microarchitectural Data Sampling Advisory
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00233.html

INTEL-SA-00228
Intel Unite® Client Advisory
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00228.html

INTEL-SA-00223
2019.1 QSR UEFI Advisory
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00223.html

INTEL-SA-00218
Intel® Graphics Driver for Windows* 2019.1 QSR Advisory
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00218.html

INTEL-SA-00213
Intel® CSME, Intel® SPS, Intel® TXE, Intel® DAL, and Intel® AMT 2019.1 QSR Advisory
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00213.html

HITB Amsterdam 2019: presentation materials online

https://conference.hitb.org/hitbsecconf2019ams/materials/
https://conference.hitb.org/hitbsecconf2019ams/conference/

3mdeb: 5 terms every hypervisor developer should know

This is the first post of a series about developing type-1 hypervisors, also known as native or bare-metal hypervisors. It introduces to Intel’s VMX technology, describes interactions between a virtual machine and a hypervisor as well as gives some insight on the control structures required. This post should give some theoretical knowledge base required for the next ones, in which we will implement a basic hypervisor using Bareflank. It assumes that you have some knowledge about IA-32 architecture. There will be more than 5 terms actually, but the most important are those in headers. The following posts will assume that the reader knows what they are for and what is their scope.

https://blog.3mdeb.com/2019/2019-04-30-5-terms-every-hypervisor-developer-should-know/

Google: Android Q: Queue the Hardening Enhancements

Google has a new blog post discussing security improvements in the latest release of Android:

https://security.googleblog.com/2019/05/queue-hardening-enhancements.html

Rust-Hypervisor-Firmware: Simple KVM firmware from Intel



This project is an experiment and should not be used production workloads. This repository contains a simple KVM firmware that is designed to be launched from anything that supports loading ELF binaries and running them with the Linux kernel loading standard. The ultimate goal is to be able to use this “firmware” to be able to load a bootloader from within a disk image. Currently it will directly load a kernel from a disk image that follows the Boot Loader Specification. Although this project has been developed using Firecracker as it does not currently support resetting the virtio block device it is not possible to boot all the way into the OS.

https://github.com/intel/rust-hypervisor-firmware

MEImageTool – Image manipulation tools for the Management Engine firmware


This set of tools allow to extract and create firmware images for the ME, and was created by Peter Bosch for personal use. […] It currently consists of three tools:


ME Region Tool: allows extracting a ME region into its constituent partitions. It produces an XML file containing the information contained within the Flash Partition Table that cannot be inferred from the files.

MFS Tool: allows extracting MFS volumes on the FAT level, MFS directories are not yet supported. The tool can also add files to volumes, but not overwrite them.

ME Config Tool: can convert intel.cfg and fitc.cfg format archives into their contents and reconstruct them. Metadata and file lists are stored in an XML archive and as such the tool does not require the host filesystem to support UNIX permissions.

https://github.com/peterbjornx/meimagetool

DMTF releases Security Protocol and Data Model (SPDM) spec

https://www.dmtf.org/content/dmtf-releases-security-protocol-and-data-model-spdm-architecture-work-progress

https://www.dmtf.org/standards/pmci

The Security Protocol and Data Model (SPDM) Specification (DSP0274) provides message exchange, sequence diagrams, message formats, and other relevant semantics for authentication, firmware measurement, and certificate management. This specification for additional security defined by SPDM has a goal of aligning component authentication and integrity objects across the industry and is being designed to be referenced by other standards organizations.

The SPDM over MCTP Binding Specification (DSP0275) will contain the mapping of SPDM to MCTP message type 5 for usage within a Platform Management Subsystem that uses DMTF’s Management Component Transport Protocol (MCTP) for communication between individual components.

OpenVizsla: a tool for developers working with USB

OpenVisla was invented 10 years ago, created almost 6 years ago and to be fair, it was very unlucky. Many people have forgotten about it, but it still can be very useful. It has a lot of potential for being used in security development. We are going to continue our research and maybe, maybe in some time, we will show what this small and relatively cheap board is capable of.

https://blog.3mdeb.com/2019/2019-04-24-usb-sniffing-with-openvizsla/