More Windows Kernel Vulnerabilities May Yet Emerge, Researcher Says
After issuing dozens of patches this year, Microsoft could still have more work to do, Black Hat speaker warns
Jul 19, 2011 | 12:46 AM |
By Tim Wilson Dark Reading
A researcher who discovered a fundamental design flaw in the kernel of the Windows operating system says the software giant has done a good job of patching so far, but it's likely that more vulnerabilities will emerge before its work is done.
Tarjei Mandt, a researcher at security company Norman ASA, says that despite last week's Patch Tuesday announcements, which corrected some 13 Windows kernel vulnerabilities -- and a series of patches issued in April that patched 30 more, there likely will be more vulnerabilities found at the Windows kernel level.
Mandt, who discovered the fundamental flaws in the 15-year-old Win32.sys operating environment, will present his findings on Windows kernel vulnerabilities in a talk that will be presented at Black Hat USA in Las Vegas next month.
The vulnerabilities -- and Mandt estimates there could be hundreds of them -- generally are the result of a function in the Win32k graphical user interface called user-mode callbacks, a mechanism that allows the kernel to make calls back into user-mode. User-mode callbacks enable the operating system to do a variety of tasks, such as invoking application-defined hooks, providing event notifications, and copying data to or from user-mode, Mandt explains.
While there are no known examples of exploits that take advantage of the Win32k vulnerabilities in the wild, the relative ease of creating such exploits -- combined with the fundamental role of the kernel in all Windows operations -- should make these vulnerabilities a top priority for patching, Mandt says.
"A flaw at the kernel level could give an attacker access to some capabilities that an application-level flaw might not," Mandt says. One of the principal threats is the ability to use the flaws to elevate user privileges, which could enable the attacker to take over a Windows device and/or execute code remotely.
By issuing 30 patches in April and another 13 last week, Microsoft has taken some strong steps in fixing the problem, Mandt says. But because flaws at the graphical user interface (GUI) level are so fundamental to the operating system, recognizing and patching them all will be a complex process, he warns.
"It's hard to say if Windows is OK at this point," Mandt says. "The problems are very complex. There probably will be more bugs, but it's hard to say how many. It's something we'll be watching closely."
Norman ASA, which makes a variety of tools ranging, from simple antivirus applications to complex malware analysis environments, specializes in Windows kernel-level security issues and tools.
Have a comment on this story? Please click "Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.
Currently we allow the following HTML tags in comments:
Single tags
These tags can be used alone and don't need an ending tag.
<br> Defines a single line break
<hr> Defines a horizontal line
Matching tags
These require an ending tag - e.g. <i>italic text</i>
<a> Defines an anchor
<b> Defines bold text
<big> Defines big text
<blockquote> Defines a long quotation
<caption> Defines a table caption
<cite> Defines a citation
<code> Defines computer code text
<em> Defines emphasized text
<fieldset> Defines a border around elements in a form
<h1> This is heading 1
<h2> This is heading 2
<h3> This is heading 3
<h4> This is heading 4
<h5> This is heading 5
<h6> This is heading 6
<i> Defines italic text
<p> Defines a paragraph
<pre> Defines preformatted text
<q> Defines a short quotation
<samp> Defines sample computer code text
<small> Defines small text
<span> Defines a section in a document
<s> Defines strikethrough text
<strike> Defines strikethrough text
<strong> Defines strong text
<sub> Defines subscripted text
<sup> Defines superscripted text
<u> Defines underlined text
Dark Reading encourages readers to engage
in spirited, healthy debate, including taking us to task.
However, Dark Reading moderates all comments posted to our site,
and reserves the right to modify or remove any content that it determines to be derogatory,
offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM.
Dark Reading further reserves the right to disable the profile of any commenter participating
in said activities.
Choosing the Right Vulnerability Scanner for Your Organization
Vulnerability scanners can be used to help detect and fix systemic problems in an organization's security program and monitor the effectiveness of security controls. However, a vulnerability scanner can improve the organization?s security posture only when it is used as part of a vulnerability management program, in which products, processes and people are working together to find, identify, prioritize and mitigate threats. Here are some tips on choosing and implementing vulnerability scanners in your enterprise.
Using Google to Find Vulnerabilities In Your IT Environment
Attackers are increasingly using a simple method for finding flaws in websites and applications: they Google them. Using Google code search, hackers can identify crucial vulnerabilities in application code strings, providing the entry point they need to break through application security. Sound scary? It is, but there is good news: You can use these same methods to find flaws before the bad guys do. In this special report, we outline methods for using search engines such as Google and Bing to identify vulnerabilities in your applications, systems and services--and to fix them before they can be exploited.
Security Pro's Guide to Patch Management
It's no longer sufficient to patch just Windows, Office and IE. With the massive array of applications now residing on enterprise PCs, and the proliferation of mobile and cloud-based applications, your business is far too vulnerable to exploitation unless you have a solid strategy for patch prioritization, deployment and quality assurance. Follow these steps to put your plan in place.
Other reports from the Vulnerability Management Tech Center: