The surface area exposed is larger, because you're allowing the browser to download and run arbitrary programs, something you don't do with unmanaged languages very much.
Edit: Also, just consider how much worse it'd be if Java apps were re-written in a language that allows buffer overflows. Enterprises already cannot get security right; even generating SQL queries results in problems. No way would those teams deal with yet another layer of security issues. Hell, I've dealt with commercial teams writing in C++ thinking a buffer overflow has "something to do with network rate limiting."
At least some of those Java vulnerabilities are logic errors in the sandboxing/securitymanager parts that are supposed to prevent applets from accessing privileged APIs, and those checks are usually implemented inside the actual java.* standard library classes, in the Java language.
The JVM is good. The Java Applet Plugin, on the other hand, is a problem.
And contrast with alternative affirmative/MAC-based sandboxing schemes like Chrome's NaCl, or OS-level stuff using SELinux/AppArmor. These don't require a managed runtime at all, and yet appear ("appear" being a critical point of courses) to solve this problem in a more robust way.
I'm not sure we really know how to secure a desktop application / fat client platform yet.
Remember ActiveX and how it was worse than Java applets?
Java applets are still far more efficient and far more powerful and have far greater operability with Java web server software than even HTML5 will have.
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
I've got Win7/64, service packs up to date, java autoinstaller thing....what else can I do?
If you're not already using ad-block, you will be amazed by how much it improves the performance of your general internet-surfing. So, besides security mindedness, there are already other good reasons for doing it.
> 56 percent of exploits blocked in Q3 use Java vulnerabilities.
So much for the idea of a managed language runtime being inherently more secure...