IT | Jan 22, 2017 | Master3395
On Modern Intel CPUs, the USB 3.0 port can be used to access the hardware debugging interface JTAG via DCI. According to a research duo at Positive Security, the availability of DCI can pose as a major vulnerability allowing the attacker gain full control of the CPU without doing much. However, a security key is required to use DCI which is disabled by default.
Hardware debugging of stuff like kernel, drivers, hypervisors, etc. on Intel CPUs can be done using the JTAG (Joint Test Action Group) interface. Earlier, JTAG debugging interface could only be accessed using a unique device which had to be connected to the motherboard.
In later versions, starting from Skylake and Kabylake processors, Intel simplified the connection process and introduced DCI (Direct Connect Interface) which allows JTAG access via the USB 3.0 port present on the machine. This is handy in the case of portable computers like laptops.
According to the Positive Security researchers, Maxim Goryachy and Mark Ermolov, the ability to access CPUs via the USB port can be dangerous. They note that the target computer could be tagged as vulnerable even if the DCI interface is just enabled, there are no software or hardware changes to be made. However, DCI is disabled by default on Intel CPUs. It can be enabled using the BIOS configuration, and a proprietary key is required to access JTAG.
The duo Goryachy and Ermolov demonstrated the vulnerability – at the Chaos Communication Congress (33C3) last year – which can be used to gain full control of the Intel CPUs. They believe that CPU access mechanisms like this can take destructive USB devices, like Killer USB, to a whole new level.
Here is the demo video:
Keywords: intel, hack, usb, cpu, kabylake
Mar 18, 2019 | Category: General | Comments
Found 82 extensions for new Edge.
As we interpret recently Microsoft's activity, we are not the long wait from a public testing period of their new Chromium-based browser. Last week we got a sneak peek at new Edge in some photos you can see here, and it was explained that the first tests only had support in 64-bit Windows 10.read more…