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.

Application Security

12/4/2019
11:00 AM
Kelly Sheridan
Kelly Sheridan
Quick Hits
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Microsoft Issues Advisory for Windows Hello for Business

An issue exists in Windows Hello for Business when public keys persist after a device is removed from Active Directory, if the AD exists, Microsoft reports.

Microsoft has issued an advisory (ADV190026) to provide guidance to businesses following the disclosure of an issue in Windows Hello for Business (WHfB). The problem exists when public keys persist following a device's removal from Active Directory, if the Active Directory exists.

The issue was discovered by Michael Grafnetter, IT security researcher and trainer for CQURE and GOPAS, who has been investigating the inner workings of WHfB and discovered multiple attack vectors for the passwordless authentication tool. One of these vectors involves msDS-KeyCredentialLink, which could potentially be used or misused for persistence by an attacker.

Today's advisory refers to another one of his findings. When someone sets up WHfB, the WHfB public key is written to the on-premises AD, and its keys are tied to a user and device that has been added to Azure AD. If the device is removed, its linked WHfB key is considered orphaned. However, these orphaned keys are not deleted, even if their corresponding device is removed. While any authentication to Azure AD using an orphaned key will be rejected, some of these WHfB keys cause a security issue in AD 2016 and 2019 in hybrid or on-premises environments.

An authenticated attacker could access orphaned keys created on Trusted Platform Modules (TPMs) affected by CVE-2017-15361, as detailed in separate security advisory ADV170012, to compute their WHfB private key using the orphaned public keys. The attacker could use the stolen private key to authenticate as the user within the domain with Public Key Cryptography for Initial Authentication (PKINIT).

"This attack is possible even if firmware and software updates have been applied to TPMs that were affected by CVE-2017-15361 because the corresponding public keys might still exist in Active Directory," Microsoft explains in its advisory. Its advisory is intended to provide guidance to clean up orphaned public keys created using an unpatched TPM, before the updates detailed in ADV170012 were applied.

So far, there is no evidence to suggest this issue has been used to attack machines in the wild, officials say. Read mitigation steps in Microsoft's full advisory here.

Check out The Edge, Dark Reading's new section for features, threat data, and in-depth perspectives. Today's top story: "A Cause You Care About Needs Your Cybersecurity Help."

Kelly Sheridan is the Staff Editor at Dark Reading, where she focuses on cybersecurity news and analysis. She is a business technology journalist who previously reported for InformationWeek, where she covered Microsoft, and Insurance & Technology, where she covered financial ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
Active Directory Needs an Update: Here's Why
Raz Rafaeli, CEO and Co-Founder at Secret Double Octopus,  1/16/2020
Google Lets iPhone Users Turn Device into Security Key
Kelly Sheridan, Staff Editor, Dark Reading,  1/15/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-16270
PUBLISHED: 2020-01-22
Samsung Galaxy Gear series before build RE2 includes the hcidump utility with no privilege or permission restriction. This allows an unprivileged process to dump Bluetooth HCI packets to an arbitrary file path.
CVE-2018-16271
PUBLISHED: 2020-01-22
The wemail_consumer_service (from the built-in application wemail) in Samsung Galaxy Gear series allows an unprivileged process to manipulate a user's mailbox, due to improper D-Bus security policy configurations. An arbitrary email can also be sent from the mailbox via the paired smartphone. This a...
CVE-2018-16272
PUBLISHED: 2020-01-22
The wpa_supplicant system service in Samsung Galaxy Gear series allows an unprivileged process to fully control the Wi-Fi interface, due to the lack of its D-Bus security policy configurations. This affects Tizen-based firmwares including Samsung Galaxy Gear series before build RE2.
CVE-2019-10780
PUBLISHED: 2020-01-22
BibTeX-ruby before 5.1.0 allows shell command injection due to unsanitized user input being passed directly to the built-in Ruby Kernel.open method through BibTeX.open.
CVE-2019-10781
PUBLISHED: 2020-01-22
In schema-inspector before 1.6.9, a maliciously crafted JavaScript object can bypass the `sanitize()` and the `validate()` function used within schema-inspector.