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.

Network Security

10/17/2017
04:11 PM
Curtis Franklin
Curtis Franklin
Curt Franklin
50%
50%

KRACK Attack: How Enterprises Can Protect Their WiFi

A flaw in the WPA2 protocol means that most WiFi networks worldwide are open to successful attack.

By this time you've probably heard about the KRACK attack, and what you've heard is right. This one is bad, and it's everywhere.

The name is an acronym taken from key reinstallation attacks, the technique used to take advantage of a vulnerability that exists in pretty much every WiFi access point in use today. The reason it's so widespread is that the vulnerability in the way WPA2 (WiFi Protected Access II) is implemented in the WiFi protocol.

Here, in a nutshell is the problem: In WPA2 there's a shared secret (the password) that a device and the access point use to begin the process, and then a single-use string (or "nonce") that is shared to actually encrypt the conversation. This happens in a process known as a four-way handshake. The vulnerability is in step three of the four-way handshake, when an attacker can force the access point to re-use a previous nonce -- a nonce that the attacker has.

Once the bogus nonce is in use, the attacker can decrypt the entire session and steal any information passing over the network. Now, if this is happening on a public network where employees have already been trained to use a VPN, then there's no real problem since sensitive traffic will travel within an ecnrypted tunnel and the encryption used by SSL and most other VPNs isn't affected by the vulnerability.

The issue is with corporate WiFi networks (and home networks where the employee has implemented WPA2) in which people have been trained to think of traffic as secure, and VPNs as unnecessary. There are few situations more dangerous than one in which people think they're far more secure than they actually are -- and this KRACK attack combines that with near ubiquity.

If there's good news to be found in all this, it's that there haven't been any attacks based on this technique identified in the wild. The news gets a little better with both Microsoft and Apple announcing that they have patches either released or in beta for their desktop and mobile operating systems (though there hasn't been any news, yet, about Apple patching the software for their Airport WiFi access points).

US-CERT has a vulnerability note on the WPA2 vulnerability and they've thoughtfully included a list of vendors affected by the problem.

So what is an enterprise to do? First, at least temporarily amend your WiFi use rules to include VPN use at all times -- even when connected to wireless networks inside the perimeter. Next, stay on top of your vendors for patches to device and access point software. Some have suggested that companies use this episode as a pass/fail test for vendors: If they don't patch vulnerable systems, and soon, then replace them with vendors that pay more attention to security.

How is your organization reponsing to KRACK? We would like to hear your stories -- let us know in the comment section, below.

Related posts:

— Curtis Franklin is the editor of SecurityNow.com. Follow him on Twitter @kg4gwa.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Manchester United Suffers Cyberattack
Dark Reading Staff 11/23/2020
As 'Anywhere Work' Evolves, Security Will Be Key Challenge
Robert Lemos, Contributing Writer,  11/23/2020
Cloud Security Startup Lightspin Emerges From Stealth
Kelly Sheridan, Staff Editor, Dark Reading,  11/24/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
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-2019-20934
PUBLISHED: 2020-11-28
An issue was discovered in the Linux kernel before 5.2.6. On NUMA systems, the Linux fair scheduler has a use-after-free in show_numa_stats() because NUMA fault statistics are inappropriately freed, aka CID-16d51a590a8c.
CVE-2020-29368
PUBLISHED: 2020-11-28
An issue was discovered in __split_huge_pmd in mm/huge_memory.c in the Linux kernel before 5.7.5. The copy-on-write implementation can grant unintended write access because of a race condition in a THP mapcount check, aka CID-c444eb564fb1.
CVE-2020-29369
PUBLISHED: 2020-11-28
An issue was discovered in mm/mmap.c in the Linux kernel before 5.7.11. There is a race condition between certain expand functions (expand_downwards and expand_upwards) and page-table free operations from an munmap call, aka CID-246c320a8cfe.
CVE-2020-29370
PUBLISHED: 2020-11-28
An issue was discovered in kmem_cache_alloc_bulk in mm/slub.c in the Linux kernel before 5.5.11. The slowpath lacks the required TID increment, aka CID-fd4d9c7d0c71.
CVE-2020-29371
PUBLISHED: 2020-11-28
An issue was discovered in romfs_dev_read in fs/romfs/storage.c in the Linux kernel before 5.8.4. Uninitialized memory leaks to userspace, aka CID-bcf85fcedfdd.