Not one Microsoft product on Kaspersky’s top 10 vulnerabilities list
81–90 of 137 posts
Re: Not one Microsoft product on Kaspersky’s top 10 vulnerabilities list
#82Earlier quoted context omitted.
Well CLR seems to be OK so I think this is down to the implementation rather than the concept.
Fewer browsers will run CLR code, so harder to do a drive-by.
Of course, these are desktop stats. On mobile, it's a different story.
[1] http://www.microsoft.com/getsilverlight/Get-Started/Install/...
[2] http://en.wikipedia.org/wiki/Microsoft_Silverlight#Adoption
[4] http://www.statowl.com/custom_ria_market_penetration.php
Re: Not one Microsoft product on Kaspersky’s top 10 vulnerabilities list
#83Earlier quoted context omitted.
It seems to me that the only reason we put up with JVM applets (whereas anyone suggesting we put up with people ActiveX would rightfully be laughed down these days) is because of that steady monotonous stream of crap about how much better Java is for security. It has dropped our collective paranoia far too low.
Java is or was until very recently as anyone who has used it since 1995 will know and remember. Recent issue have arisen, hopefully Oracle is going to get its track record up to what Sun's was. Until then, a few bad recent reports for Java 7 will not wipe out decades of countless security reports for all of Windows Operating System and many relied upon Windows applications. Java applets are still far more efficient a…
Re: Not one Microsoft product on Kaspersky’s top 10 vulnerabilities list
#84Reading http://www.securelist.com/en/analysis/204792250/IT_Threat_Ev... , I find it surprising that the Netherlands manages to be the best malware exporter in the world (third in 'production', close behind Russia and the USA (both with a much larger population), but also in the top 10 for 'least consumption', a list that neither Russia nor the USA made). Does anybody have any idea how that comes about? The only reaso…
(I have no data to back this up...)
Re: Not one Microsoft product on Kaspersky’s top 10 vulnerabilities list
#85Let's take a look at CERT, shall we? 17 Sep 2012 VU#480095 Microsoft Internet Explorer 6/7/8/9 contain a use-after-free vulnerability 17 Sep 2012 VU#389795 Windows Phone 7 does not check certificate Common Names when sending or receive Hmm. OK, how about #1 service being remotely attacked right now: MS Terminal Services
[1] By "Common Vulnerability Scoring System": http://www.kb.cert.org/vuls/byCVSS
[2] By Date: http://www.kb.cert.org/vuls/bypublished
Re: Not one Microsoft product on Kaspersky’s top 10 vulnerabilities list
#86It's actually this bit from farther down that surprised me the most: > 56 percent of exploits blocked in Q3 use Java vulnerabilities. So much for the idea of a managed language runtime being inherently more secure...
I've got Win7/64, service packs up to date, java autoinstaller thing....what else can I do?
Re: Not one Microsoft product on Kaspersky’s top 10 vulnerabilities list
#87Earlier quoted context omitted.
The problem mostly isn't the runtime itself, but instead the various 3rd party modules (all of which are written in late-90's-era C/C++) that get hooked up to the JVM. For instance, the Quicktime API for Java exposed scalar integers, intended to be "opaque", but in fact raw memory locations. The JVM is good. The Java Applet Plugin, on the other hand, is a problem.
Well, sure. But I think that's maybe missing my point -- a managed runtime needs "holes" in it to do its job, which exposes the security problems of the rest of the system via inevitably leaky abstractions. The point was that the managed runtime does nothing to address this, it has to drill down to a C API at some point (or deeper, consider a similar hole in a shader compiler or video codec accelerator). And contrast…
Re: Not one Microsoft product on Kaspersky’s top 10 vulnerabilities list
#88Earlier quoted context omitted.
What can we trace this security priority initiative of Microsoft back to?
Jan 15, 2002 email from Bill Gates to all MSFT staff [1]. Includes some real gems, like; >So now, when we face a choice between adding features and resolving security issues, we need to choose security. Our products should emphasize security right out of the box, and we must constantly refine and improve that security as threats evolve. 1. http://www.wired.com/techbiz/media/news/2002/01/49826
Spot on. 2002.