This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Recently, JRE and Java apps running on browsers are considered to be potential security threats. In Firefox, it is deactive by default. Why suddenly Java is considered to be security threat? Although, nowadays we don't use applets for most of the browser applications (Rules round-up on Javaranch could be an exception ).
Is this security vulnerability applicable to server side applications running on Java?
There's nothing "sudden" about this. There have been vulnerabilities (and attendant attacks) on client-side JVMs for at least 15 years, just like there have been on Flash, Silverlight and other client-side technologies ever since they were created.
What's changed is the mindset of people (certainly heightened recently by all the talk about what the NSA is up to), and -in client-side Java's case- a sense that it is outdated technology, and so accepting the security weaknesses no longer outweighs the benefits of using it.
Java has had vulnerability reports throughout most of its lifetime. Most of these were bugs in the underlying C code that implemented Java.
The recent Java exploits are a different breed entirely, in that they relied on 'pure Java'. They had nothing to do with C. Many of them were discovered 18 months ago by Security Explorations. They allowed Java applets to escape the Java sandbox, and run with the same privileges as your web browser.
Server side applications are a complex story...it depends on the framework you are using. Servlets running under programs like Apache Tomcat are vulnerable, as Tomcat uses Java's security sandbox to protect itself from malicious servlets. So today a malicious servlet could crash Tomcat, or, worse, corrupt how it runs.
But other frameworks that don't use Java's SecurityManager are not vulnerable to these recent exploits.