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.

Risk

1/26/2008
07:35 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

Recent Vista Metrics: Don't Be Fooled

Microsoft's security strategy director, Jeff Jones' recent report card bestowing high marks on the security of his employer's most recent operating system release has garnered plenty of ink. But what's it mean?

Microsoft's security strategy director, Jeff Jones' recent report card bestowing high marks on the security of his employer's most recent operating system release has garnered plenty of ink. But what's it mean?The good is that the number of first-year Windows vulnerabilities is trending down. Jones even put his neck (way, way) out detailing how Vista's vulnerability counts are lower than most every other operating system on the market. So much for not tooting your own horn. The bad news is that there are still too many vulnerabilities being uncovered. And the truth is that straight-up vulnerability count comparisons between operating systems don't tell you much.

First, kudos to Microsoft for sticking to its Trustworthy Computing efforts. Those efforts kicked off in 2002, and the results are starting to show in a big way. In fact, Vista is the first operating system to go completely through Microsoft's secure development processes - and the number of vulnerabilities has been cut nearly in half.

That means the quality of Microsoft's operating system has improved. And that's great news for its customers. It does not mean you are inherently more secure using Vista. Even the fact, by Microsoft's count, that Vista garnered fewer vulnerabilities in the first 12 months of public availability than Red Hat rhel4ws, Ubuntu 6.06 LTS, and Apple Mac OS X 10.4 doesn't make it more secure by choosing Vista. And for the case I'm making here, I mean more secure in actual, real-world, use.

While the report, available here, is interesting, it's just a start at evaluating the overall security of the operating system. These vulnerability counts may be good for Microsoft's own efforts at quality improvement, but by simply knowing that Microsoft fixed 36 vulnerabilities in Vista, versus 65 for XP doesn't amount to much for the rest of us.

In his report, Jones' writes that fewer vulnerabilities "make it easier to manage risk." As well as this: "All other things being equal, fewer patches mean more time to spend on other security projects to reduce risk. Not necessarily so. I'd take 100 low-risk vulnerabilities that can be rolled into standard system updates any day over 12 highly critical vulnerabilities that need to be patched post-haste.

In order to judge the security of one operating system over another requires a lot more than mere vulnerability counts. You need to take a look at how these vulnerabilities can be exploited: can they be remotely exploited? What is the result of compromise? Is there anything in the operating system that mitigates the risk to other applications or system processes? And how actively is the operating system being targeted?

That last point is especially important when judging the overall "safety" of using any operating system. An obscure operating system isn't going to be targeted by active exploits and malware as often as the 90% plus industry giant.

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/23/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Russian Military Officers Unmasked, Indicted for High-Profile Cyberattack Campaigns
Kelly Jackson Higgins, Executive Editor at Dark Reading,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-24847
PUBLISHED: 2020-10-23
A Cross-Site Request Forgery (CSRF) vulnerability is identified in FruityWifi through 2.4. Due to a lack of CSRF protection in page_config_adv.php, an unauthenticated attacker can lure the victim to visit his website by social engineering or another attack vector. Due to this issue, an unauthenticat...
CVE-2020-24848
PUBLISHED: 2020-10-23
FruityWifi through 2.4 has an unsafe Sudo configuration [(ALL : ALL) NOPASSWD: ALL]. This allows an attacker to perform a system-level (root) local privilege escalation, allowing an attacker to gain complete persistent access to the local system.
CVE-2020-5990
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in the ShadowPlay component which may lead to local privilege escalation, code execution, denial of service or information disclosure.
CVE-2020-25483
PUBLISHED: 2020-10-23
An arbitrary command execution vulnerability exists in the fopen() function of file writes of UCMS v1.4.8, where an attacker can gain access to the server.
CVE-2020-5977
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in NVIDIA Web Helper NodeJS Web Server in which an uncontrolled search path is used to load a node module, which may lead to code execution, denial of service, escalation of privileges, and information disclosure.