Risk
7/24/2008
07:35 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Disclosure Isn't Working

After a decade of writing about IT security, I don't know how anyone would think this current system of disclose and patch is working. It's not.

After a decade of writing about IT security, I don't know how anyone would think this current system of disclose and patch is working. It's not.Do you know when the riskiest time for an attack against a vulnerability is? Is it:

1) When a vulnerability has been discovered by a security researcher? 2) While the vendor is working on a patch? 3) Right after the vulnerability has been disclosed and the patch announced?

If you answered 3, you win.

Once the patch has been released, any security researchers or cybercriminals worth their salt can reverse-engineer the patch and find the vulnerability to attack. Which they do -- within days, if not hours, and then, undoubtedly, begin attacking the legions of unpatched systems.

But you're thinking, "The software flaw was always there, and we've been susceptible all along to attack!"

You're just looking at one variable of the risk equation (note: Cost should be factored in for enterprises, but it's not necessary now):

Risk = Threat x Vulnerability

By this equation, when a vulnerability exists in a software application and no one knows about it, there's no risk because there's no threat to its exploitation. But once a vulnerability is discovered and more people know about it, the higher the risk. Too often in this industry, we all focus on Vulnerability and not Threat.

Now, let's assume that shiny new browser you installed -- we'll call it ExplorerFox Opera -- has 100 vulnerabilities the day it's released, but no one knows that they're there. You're risk to attack is now low.

But in a few days criminal hackers find 10 flaws to exploit. Your risk is now high, and attackers begin infecting people with keystroke loggers and spyware. A week later, white-hat security researchers find 10 -- completely different flaws -- and they call the makers of ExplorerFox Opera to have patches made, and within a month or two all of those flaws found by the white hats are patched. How much more secure are you now? You're still at risk from the 10 vulnerabilities being attacked in the underground, and there are 80 flaws still left to be discovered by good and bad guys alike. Who will find them?

But wait, the show goes on: News reports start surfacing of those 10 zero-day flaws being actively exploited, and the makers of ExplorerFox Opera rush out a set of new patches to fix those.

But security researchers find that those patches actually create more vulnerabilities than they fixed ...

If only we built and maintained buildings, cars, airplanes, oil refineries, and nuclear power plants this way.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.