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.

Vulnerabilities / Threats

4/10/2018
05:10 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Microsoft Issues Rare Patch for Wireless Keyboard Flaw

Patch Tuesday includes 67 fixes - the most critical of which are browser-related.

So much for a spring break: Microsoft today dropped 67 security patches in its April Patch Tuesday release, including one for a piece of one of its hardware devices, the Wireless Keyboard 850.

Hardware – and keyboard – patches are relatively rare, so the security bypass vulnerability Microsoft fixed today in the keyboard stood out among the typical security flaws, which included 24 critical bugs, 42 rated as important, and one as moderate. Microsoft rated the keyboard vuln (CVE-2018-8117) as "important."

The flaw allows an attacker to reuse the keyboard's AES encryption key in order to log keystrokes, or inject them into the affected keyboard devices. According to Microsoft, "an attacker could simulate keystrokes to send malicious commands into a victim's computer" or "read keystrokes such as passwords sent by other keyboards for the affected devices."

Such an attack would be no simple feat: it requires physical proximity, and the attacker would have to pilfer the encryption key from the vulnerable keyboard. The patch forces each wireless keyboard to generate a unique AES encryption key.

Dustin Childs, communications manager for ZDI, says keyboard patching is rare, mainly because most vendors of the hardware devices don't have the update infrastructure like Microsoft has nor the ability to track them for updates. "Microsoft has the operating system where it can update" them, Childs notes. While the attack would require some finesse and sophistication, it's still worth applying the patch in short order, albeit not as a top priority compared with other updates in this month's patch batch, according to Childs.

"If I know I have this keyboard in my enterprise, I'm not going to ignore this patch," he says, noting that open work environments would be more at risk of such an attack.

Microsoft didn't detail how an attacker would steal the encryption key. But Jimmy Graham, director of product management at Qualys, says it appears to be a hardware or side-channel attack, based on the way Microsoft is blocking access to the key with the fix.

Graham points out that most of the critical bugs patched today have to do with browsers. He recommends those patches as priority for endpoints.

Microsoft also patched five critical flaws in the Windows Font Library that each allow remote code execution via Web or file-sharing attacks. Both Graham and Childs consider these patches priorities as well. "Browser [updates] are always important and near the top" as a priority, Childs says.

The Microsoft Graphics Remote Code Execution vuln flaws: CVE-2018-1010CVE-2018-1012CVE-2018-1013CVE-2018-1015, and CVE-2018-1016 could allow an attacker to tuck malicious code into fonts. Malicious fonts can be used in Web browsing and documents and attachments.

"According to Microsoft, these vulnerabilities can be exploited through a Web-based attack, meaning the user only needs to visit a malicious Web page. This could be through a compromised site or malicious ad server," Qualys' Graham says. "The other attack vector is file-based, meaning a document could be sent via email or through a fileshare that would run the exploit if opened."

Childs says these flaws are reminiscent of the Duqu nation-state group's methods. The attackers behind Duqu embedded the Duqu dropper into type fonts via the Win32k TrueType font parsing engine. "Fonts are everywhere, so always put these" vulns at a high priority, he says.

Related Content:

Interop ITX 2018

Join Dark Reading LIVE for an intensive Security Pro Summit at Interop IT X and learn from the industry’s most knowledgeable IT security experts. Check out the agenda here.Register with Promo Code DR200 and save $200.

Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio
 

Recommended Reading:

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
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...