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.


04:03 AM
Connect Directly

Bugs With No Bite

Microsoft, industry researchers say not all security vulnerabilities reported are exploitable

The dirty little secret about security bugs is not every single vulnerability that gets reported is exploitable -- meaning there are some that an attacker can't use against you. So how do you know which threats to patch right away and which to ignore?

There's no real formula for this, and even some security experts are divided on which bugs are not actually exploitable. "There is a lot of controversy among researchers about which announcements really pan out to exploitable vulnerabilities," says Thomas Ptacek, a researcher with Matasano Security. "When researchers publish advisories, people suspect the flaws are harder to exploit than they sound. When vendors publish, people suspect it's easier. The balance probably favors researchers.

"I'd guess 80 percent of what's announced turns out to be readily exploitable, and 10 to 15 percent more are refined into something dangerous down the road."

Microsoft's Security Response Center (MSRC) vets each and every bug that gets reported for its products. "We'll investigate any reported vulnerability sent to us, from a third-party ISV, a hacker mailing list, whatever," says Mike Reavey, a security program manager at the MSRC.

Those vulnerabilities Microsoft patches and considers the most dangerous are labeled as "critical," and ones that are harder to exploit get a lower severity rating, he says.

But sometimes, bugs that get reported just don't pan out, says Mark Griesi, a security program manager at the MSRC. "There are times when things that are reported as vulnerabilities quite frankly are just not," Griesi says. "Someone might report something that can circumvent a security measure in the OS, for example, but in reality, it requires someone sitting at the machine doing it themselves, on purpose. That isn't a vulnerability."

Some researchers are skeptical about the weaker or non-exploitable flaws: David Maynor, CTO of Errata Security, says not all bugs require you to buy a new security tool or to drop everything and patch. "Just because you find a bug doesn't mean it's going to be exploitable," Maynor says. "That's most of what our [Errata's] business is about: Do you really have to stop and buy new security to fix this... if [an attacker] can't do anything useful with it?"

"Not all software flaws are security vulnerabilities," he says. Just because an attacker can take advantage of a weakness or hole doesn't mean he can do any damage with it, Maynor notes. He points to the recent Universal Plug and Play bug in Microsoft's XP. Errata found in its research that the bug wasn't truly exploitable, he says. Maynor considers Microsoft's recent DNS Server Service bug -- also "critical" -- as serious, however. "The DNS bug was a big deal."

RSnake, a.k.a. Robert Hansen, founder of SecTheory, says sometimes you just can't get at a bug. "I remember one researcher telling me he's just waiting for someone to 'fix' an issue which will make the browser exploitable."

Worthless bugs don't get reported because they'd get laughed out of the security community, anyway, he says. "Most people aren't interested unless it's [the bug] remotely exploitable... That's pretty short-sighted, but it is what it is."

Microsoft's Reavey notes that not every critical vulnerability Microsoft patches will actually get exploited by an attacker.

But Microsoft doesn't try to outguess whether an attacker will or will not go for it. "Just because they haven't figured out how to exploit it today doesn't mean they won't figure it out tomorrow or a year from now," Microsoft's Griesi says. Microsoft doesn't take any chances with potentially critical bugs, he adds.

Researchers agree that in the end, it's better safe than sorry: "Even the most dedicated researchers can't quickly tell you whether a new memory corruption finding is absolutely not exploitable -- there's no silver bullet answer," Ptacek says. "Enterprises should probably assume the worst about every advisory."

Says Maynor: "It's never a bad thing to install patches."

— Kelly Jackson Higgins, Senior Editor, Dark Reading

  • Microsoft Corp. (Nasdaq: MSFT)
  • Matasano Security LLC
  • Errata Security Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

    Recommended Reading:

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Newest First  |  Oldest First  |  Threaded View
    COVID-19: Latest Security News & Commentary
    Dark Reading Staff 5/28/2020
    Stay-at-Home Orders Coincide With Massive DNS Surge
    Robert Lemos, Contributing Writer,  5/27/2020
    Register for Dark Reading Newsletters
    White Papers
    Cartoon Contest
    Write a Caption, Win a Starbucks Card! Click Here
    Latest Comment: Can you smell me now?
    Current Issue
    How Cybersecurity Incident Response Programs Work (and Why Some Don't)
    This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
    Flash Poll
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    PUBLISHED: 2020-05-29
    There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
    PUBLISHED: 2020-05-29
    A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
    PUBLISHED: 2020-05-29
    All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
    PUBLISHED: 2020-05-29
    All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
    PUBLISHED: 2020-05-29
    All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.