Security circles were thrown into disarray late last year when serious bugs known as Meltdown and Spectre threatened to leak private data from computers around the world. The industry spent months developing patches while the public remained unaware of the danger. Updates only began rolling out early this year, and many of them have been buggy or downright broken. In fact, it sounds like Microsoft’s Meltdown patch didn’t even make Windows 7 more secure. It actually did the opposite.
Meltdown and Spectre are so dangerous because they affect one of the most important low-level features of CPUs known as speculative execution. That’s a process by which a processor can perform calculations you are likely to need before being instructed to do so. The result is improved system responsiveness. However, Meltdown and Spectre can allow a rogue process to take advantage of speculative execution and read all active memory, including sensitive data like passwords.
These vulnerabilities affected most modern CPU designs, particularly Intel’s chips. Microsoft has to deal with virtually all CPU architectures, so its patches are particularly important. Swedish security researcher Ulf Frisk reports that Microsoft’s patch for Meltdown doesn’t prevent data leakage on Windows 7. It actually accelerated the process of reading secure data instead. Originally, Meltdown could allow a process to read memory at a rate of 120Kbps, but that increased to multiple gigabits per second after the patch.
According to Frisk, the new flaw affects most versions of Windows 7 and Server 2008 R2. The issues stem from a single bit in the kernel page tables memory translator that controls access permissions for kernel memory. That bit was accidentally flipped from supervisor-only to any user. Thus, all users of a system have unfettered access to the kernel page tables, but it should only be accessible to the kernel.
Frisk created a proof-of-concept exploit, which runs on 64-bit versions of Windows 7 and Server 2008 R2. The PLM4 page table is in a fixed memory location, so no “fancy” tricks are needed to utilize the Meltdown attack. After gaining read-write access, you can read all the physical memory at a much faster rate than before the patch.
A fix for the exploit in the last patch has already been developed. Microsoft began rolling it out on Tuesday. All users of Window 7 or Server 2008 R2 should manually run the update checker if they haven’t already. Hopefully, this is the last do-over Microsoft will need to get these exploits blocked.
Should Spectre, Meltdown Be the Death Knell for the x86 Standard?
Spectre and Meltdown are serious CPU flaws, but do they warrant throwing out the entire closed-source CPU model?
Microsoft Pulls Spectre, Meltdown Patches for Older AMD Systems
Microsoft has halted the distribution of patches for Spectre, Meltdown on some AMD systems due to problems with BSODs and bricked systems.
AMD Releases Updated Risk Guidance on Meltdown, Spectre
AMD has clarified its own weaknesses against Spectre and Meltdown. One week later, things aren't quite as rosy as AMD hoped they'd be.