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

11/20/2019
06:00 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

MSFT Jumps on DoH

Microsoft has announced that an upcoming version of Windows 10 will have support for DNS over HTTPS.

Microsoft has announced that an upcoming version of Windows 10 will have support for DNS over HTTPS (also called DoH) built into the Windows DNS client. This is a major change in how Domain Name System queries will be handled by the OS, and fits in with some evolving efforts that are going on industry-wide.

DNS over HTTPS proposals that have seen light will have the effect of preventing on-path eavesdropping, spoofing and blocking of DNS requests.

Domain Name System (DNS) is the Internet's naming protocol. It translates names like example.com into the actual numeric IP address of a destination server. Currently, this is done in plaintext which can -- for example -- be recorded by an internet service provider and ascribed to a user. Indeed, some ISPs have found the compiling of this data to be a major revenue stream for them.

But ISPs say that they are concerned that DoH use will complicate the use of captive portals, which are used to intercept connections briefly to force users to log on to a network, and will make it more difficult to block content at the resolver level.

The ISPs are also concerned that browser makers will cut them out of the future DNS action by directing DNS traffic to specific resolvers that the makers can choose. This would contribute to the centralization of Internet infrastructure, as thousands of DNS resolvers used for web requests would be replaced by a small handful. DoH advocates, like Mozilla and the EFF, have responded by suggesting the ISPs create the DoH DNS resolution servers themselves, and by including in DoH proposals a way to allow users to choose specific resolvers.

DoH will add a layer of privacy-enhancing encryption to DNS traffic, but it comes at a price. Even MSFT says, "Providing encrypted DNS support without breaking existing Windows device admin configuration won't be easy." They realize that in order to keep the DNS decentralized, it will be important for client operating systems (such as Windows) and Internet service providers alike to widely adopt encrypted DNS.

MSFT says that it is prioritizing DoH support as the most likely to provide immediate value "to everyone." DoH allows them to reuse existing HTTPS infrastructure, for example.

To make things work with less friction, MSFT says their upcoming DoH system, "will look for opportunities to encrypt Windows DNS traffic without changing the configured DNS resolvers set by users and system administrators."

They are starting by using DoH for DNS servers Windows is already configured to use. Windows will just use classic DNS (without encryption) to that server. However, since these servers and their DoH configurations are well known, Windows can automatically upgrade to DoH while using the same server. And if both endpoints support encryption, they say that "there's no reason to wait around for permission to use encryption."

MSFT sees DoH (or a variant) as inevitable in the future. With this advisory, they are reassuring their customers that they will not leave them with obsolete systems.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Look Beyond the 'Big 5' in Cyberattacks
Robert Lemos, Contributing Writer,  11/25/2020
Why Vulnerable Code Is Shipped Knowingly
Chris Eng, Chief Research Officer, Veracode,  11/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: We are really excited about our new two tone authentication system!
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-4126
PUBLISHED: 2020-12-01
HCL iNotes is susceptible to a sensitive cookie exposure vulnerability. This can allow an unauthenticated remote attacker to capture the cookie by intercepting its transmission within an http session. Fixes are available in HCL Domino and iNotes versions 10.0.1 FP6 and 11.0.1 FP2 and later.
CVE-2020-4129
PUBLISHED: 2020-12-01
HCL Domino is susceptible to a lockout policy bypass vulnerability in the LDAP service. An unauthenticated attacker could use this vulnerability to mount a brute force attack against the LDAP service. Fixes are available in HCL Domino versions 9.0.1 FP10 IF6, 10.0.1 FP6 and 11.0.1 FP1 and later.
CVE-2020-9115
PUBLISHED: 2020-12-01
ManageOne versions 6.5.1.1.B010, 6.5.1.1.B020, 6.5.1.1.B030, 6.5.1.1.B040, ,6.5.1.1.B050, 8.0.0 and 8.0.1 have a command injection vulnerability. An attacker with high privileges may exploit this vulnerability through some operations on the plug-in component. Due to insufficient input validation of ...
CVE-2020-9116
PUBLISHED: 2020-12-01
Huawei FusionCompute versions 6.5.1 and 8.0.0 have a command injection vulnerability. An authenticated, remote attacker can craft specific request to exploit this vulnerability. Due to insufficient verification, this could be exploited to cause the attackers to obtain higher privilege.
CVE-2020-14193
PUBLISHED: 2020-11-30
Affected versions of Automation for Jira - Server allowed remote attackers to read and render files as mustache templates in files inside the WEB-INF/classes & <jira-installation>/jira/bin directories via a template injection vulnerability in Jira smart values using mustache partials. The ...