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

12/4/2008
06:40 AM
Keith Ferrell
Keith Ferrell
Commentary
50%
50%

2% Of Windows PCs Are Patched. The Rest -- YIKES!

Think your PCs are fully patched? Think again. New research from Secunia shows less than 2 percent of the world's PCs are completely patched. And the situation's getting worse.

Think your PCs are fully patched? Think again. New research from Secunia shows less than 2 percent of the world's PCs are completely patched. And the situation's getting worse.According to Danish security firm Secunia. the state of PC patching is terrible.

Based on data collected from installations of its free vulnerability testware, Personal Software Inspector (PSI), only 1.91 percent of Windows-based PCs are fully patched.

That leaves 98 out of every 100 PCs with at least one program possessing a patchable vulnerability that's still vulnerable. Probably more than one.

In fact, Secunia says it found more than 11 patchable vulnerabilities on close to half the PCs it reviewed.

It gets better (or worse): Secunia's numbers are based on data collected over the past week or so, since the late November release of PSI 1.0.

As the company notes in a blog,the newness of the numbers tilts the research a bit. noting that these findings "are to be considered 'best case' scenarios, the real numbers are likely to be worse."

In some ways, the numbers already are worse. Take a look at this blog from nearly a year ago, when PSI was beta; back then, a whopping 4.5 percent of PCs were fully patched.

Where do your PCs stand (or fall) on the patched/non-patched chart? Find out for yourself:

PS1 1.0 is available for free download here.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
Black Hat Q&A: Hacking a '90s Sports Car
Black Hat Staff, ,  11/7/2019
The Cold Truth about Cyber Insurance
Chris Kennedy, CISO & VP Customer Success, AttackIQ,  11/7/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16863
PUBLISHED: 2019-11-14
STMicroelectronics ST33TPHF2ESPI TPM devices before 2019-09-12 allow attackers to extract the ECDSA private key via a side-channel timing attack because ECDSA scalar multiplication is mishandled, aka TPM-FAIL.
CVE-2019-18949
PUBLISHED: 2019-11-14
SnowHaze before 2.6.6 is sometimes too late to honor a per-site JavaScript blocking setting, which leads to unintended JavaScript execution via a chain of webpage redirections targeted to the user's browser configuration.
CVE-2011-1930
PUBLISHED: 2019-11-14
In klibc 1.5.20 and 1.5.21, the DHCP options written by ipconfig to /tmp/net-$DEVICE.conf are not properly escaped. This may allow a remote attacker to send a specially crafted DHCP reply which could execute arbitrary code with the privileges of any process which sources DHCP options.
CVE-2011-1145
PUBLISHED: 2019-11-14
The SQLDriverConnect() function in unixODBC before 2.2.14p2 have a possible buffer overflow condition when specifying a large value for SAVEFILE parameter in the connection string.
CVE-2011-1488
PUBLISHED: 2019-11-14
A memory leak in rsyslog before 5.7.6 was found in the way deamon processed log messages are logged when $RepeatedMsgReduction was enabled. A local attacker could use this flaw to cause a denial of the rsyslogd daemon service by crashing the service via a sequence of repeated log messages sent withi...