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.

Comments
Security Flaws Discovered in 40 Microsoft-Certified Device Drivers
Newest First  |  Oldest First  |  Threaded View
tdsan
50%
50%
tdsan,
User Rank: Ninja
8/27/2019 | 11:39:26 AM
Re: Need Access? Not hard to do if it's built in your country...
I agree with that point whole-heartedly, the supply chain process has to be improved in order to validate and verify if the existing solution has been compromised. I do think there needs to be baseline supplied by the OEM (vendor), when the system deviates from one micron or determine if there is something communicating with the outside world, then it needs to be re-examined. That will take a major budget at the very beginning to ensure the devices are measured to the nth degree before they are distributed to the public or utilize robotics to help with the measuring process.

I think we need to learn from the residual effects "Super-Micro" had on the economy - Bloomberg Article



The key will be the supply chain after we get a handle on that, then we will be able to move forward, but until then, we are just guessing.

T
Jon M. Kelley
50%
50%
Jon M. Kelley,
User Rank: Moderator
8/26/2019 | 11:12:48 AM
Need Access? Not hard to do if it's built in your country...
Access to the hardware could be hard to achieve at scale for a typical hacker or even hacking team, but within a country that builds many of the motherboards currently in use worldwide, it could easily be part of the cost of running the business. 
tdsan
50%
50%
tdsan,
User Rank: Ninja
8/13/2019 | 12:11:07 PM
This is the key - "need access to the device"
If users bring in their own equipment (BYOD), this is going to be a problem. Even if the system is not connected to the private/domain network, this still gives the actor the ability to exploit the network by allowing the device to communicate with the outside world like a "Zombie" or they can utilize a cable that connects to a machine with malware (KnowBe4 showed this in an earlier video, found on youtube). It seems we may have to move our solutions to be more Linux centric but that did not help either (maybe ChromeOS, does not allow to install unknown software), not sure what the answer is here except to keep the systems update-to-date (patching), this is interesting.

It seems MS needs to do a better job of validating the drivers before stating they have been certified.

T


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Enterprise Cybersecurity Plans in a Post-Pandemic World
Download the Enterprise Cybersecurity Plans in a Post-Pandemic World report to understand how security leaders are maintaining pace with pandemic-related challenges, and where there is room for improvement.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-21533
PUBLISHED: 2021-09-16
fig2dev 3.2.7b contains a stack buffer overflow in the read_textobject function in read.c.
CVE-2020-21534
PUBLISHED: 2021-09-16
fig2dev 3.2.7b contains a global buffer overflow in the get_line function in read.c.
CVE-2020-21535
PUBLISHED: 2021-09-16
fig2dev 3.2.7b contains a segmentation fault in the gencgm_start function in gencgm.c.
CVE-2020-21529
PUBLISHED: 2021-09-16
fig2dev 3.2.7b contains a stack buffer overflow in the bezier_spline function in genepic.c.
CVE-2020-21530
PUBLISHED: 2021-09-16
fig2dev 3.2.7b contains a segmentation fault in the read_objects function in read.c.