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
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2208
Published: 2014-12-28
CRLF injection vulnerability in the LightProcess protocol implementation in hphp/util/light-process.cpp in Facebook HipHop Virtual Machine (HHVM) before 2.4.2 allows remote attackers to execute arbitrary commands by entering a \n (newline) character before the end of a string.

CVE-2014-2209
Published: 2014-12-28
Facebook HipHop Virtual Machine (HHVM) before 3.1.0 does not drop supplemental group memberships within hphp/util/capability.cpp and hphp/util/light-process.cpp, which allows remote attackers to bypass intended access restrictions by leveraging group permissions for a file or directory.

CVE-2014-5386
Published: 2014-12-28
The mcrypt_create_iv function in hphp/runtime/ext/mcrypt/ext_mcrypt.cpp in Facebook HipHop Virtual Machine (HHVM) before 3.3.0 does not seed the random number generator, which makes it easier for remote attackers to defeat cryptographic protection mechanisms by leveraging the use of a single initial...

CVE-2014-6123
Published: 2014-12-28
IBM Rational AppScan Source 8.0 through 8.0.0.2 and 8.5 through 8.5.0.1 and Security AppScan Source 8.6 through 8.6.0.2, 8.7 through 8.7.0.1, 8.8, 9.0 through 9.0.0.1, and 9.0.1 allow local users to obtain sensitive credential information by reading installation logs.

CVE-2014-6160
Published: 2014-12-28
IBM WebSphere Service Registry and Repository (WSRR) 8.5 before 8.5.0.1, when Chrome and WebSEAL are used, does not properly process ServiceRegistryDashboard logout actions, which allows remote attackers to bypass intended access restrictions by leveraging an unattended workstation.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.