Windows RT: Bug not a bug?

Microsoft, kernel expert take sides on whether this week's Windows RT flaw is a security vulnerability that needs to be patched

By , Computerworld |  Windows, Windows RT

"The scenario outlined is not a security vulnerability and does not pose a threat to Windows RT users," Microsoft categorically said Tuesday in a statement. The company also hinted at its rationale: "The mechanism described is not something the average user could, or reasonably would, leverage as it requires local access to a system, local administration rights and a debugger in order to work," Microsoft said.

True, acknowledged Mandt, who admitted clrokr's tactic had flaws. "Although the attack in this case can be used to disable [Windows RT's] signature enforcement at runtime, launching something that can survive a reboot is a completely different story due to the extensive verification made by UEFI Secure Boot," Mandt said.

UEFI Secure Boot is a security measure supported by Windows RT -- and its parent, Windows 8 -- that blocks unsigned code from running at boot time, essentially quashing malware attempting to inject itself into the boot process.

Because of Secure Boot, clrokr's bypass can't survive a reboot, meaning that the kernel bug would have to be re-triggered, and the unauthorized app re-installed, each time the device is turned on.

"If it didn't require this step, then the threat would be much more severe, as it could easily be bundled as a payload in a browser exploit or [something] similar," said Mandt. "In order to survive a reboot, additional steps would need to be taken such as leveraging additional vulnerabilities."

Although those hypothetical vulnerabilities have yet to be found, Mandt was concerned enough about the possibility to urge Microsoft to fix the bug and harden Windows RT.

"Once the executable is running, there are no mechanisms that prevent the attacker from modifying the code in memory," Mandt observed. "If Microsoft adopted a code-signing scheme similar to that of iOS, as well as addressed obvious kernel information disclosure techniques such as the one used by clrokr, then exploitation of these vulnerabilities would be notably harder."

Without such changes, Mandt believed that Windows RT, like iOS, would eventually be jailbroken, leaving it open to attack by malicious code posing as a desktop application. "It seems likely that Windows RT will be permanently jailbroken at some point," he said. "Windows RT tries to be a hybrid tablet and desktop OS, unlike Apple's iOS which is a very stripped-down version of OS X. This offers a lot more attack surface and, in theory, should make it easier for an attacker to jailbreak the device."

Microsoft left the change door open, telling other news outlets earlier in the week, "We'll not guarantee these approaches will be there in future releases."

Originally published on Computerworld |  Click here to read the original story.
Join us:






Answers - Powered by ITworld

ITworld Answers helps you solve problems and share expertise. Ask a question or take a crack at answering the new questions below.

Ask a Question