News for hackers. Stuff that matters.
Re:Preventing heartbleed bugs with safe programming languages by lmm on Friday April 11, 2014 @06:24AM (#7572086)
> After 20 years of Java we still don't have our perfect VM. It still sees critical security vulnerabilities.

Sure, but how many, and how often? The last advisory for Java's SSL I can find is from 2009, and that was quite a limited flaw (allowed an attacker to inject a prefix into SSL data). Indeed the kind of exposure we see with heartbleed - leaking all of the process's memory including the private key - is more or less impossible by design. At this point maybe using Java for your internet-facing service might do more to improve your security than shaving a day off your response time.

Re:Preventing heartbleed bugs with safe programming languages by eatfish on Friday April 11, 2014 @06:41AM (#7572124)
Sorry, I'm not limiting the discussion to SSL vulnerabilities.

A remote code exploit is as bad as a memory leak.

I posted these two: CVE-2013-1493 and CVE-2013-0809 in another reply. These 2 were memorable to me just because visiting a page (or a compromised page) would allow the exploit to proceed without any password/prompt/warning.

Re:Preventing heartbleed bugs with safe programming languages by lmm on Friday April 11, 2014 @09:40AM (#7572743)
CVE-2013-1493 is more an argument for java - the vulnerability exists because that part of the standard library is implemented as native code rather than in java itself.