Nothing in life is completely secure; Java is no exception. Several specific security problems have been discovered and fixed since Java was first released. If you're using an up-to-date Web browser, you are usually safe against the known attacks. However, nobody is safe against attacks that haven't been discovered yet.
If somebody says Java is safe because ``hackers aren't smart enough to exploit the problems,'' don't believe them. We're disappointed that some people who should know better are still spouting this nonsense. We've discovered several security problems, and we're pretty sure we're not the smartest people in the world. If one group of hackers creates a Java-based attack and shares it with their friends, we're all in trouble.
Other Web ``scripting'' tools such as JavaScript, Visual Basic Script, or ActiveX face the same sorts of problems as Java. ``Plug-in'' mechanisms provide no security protection. If you install a plug-in, you're trusting that plug-in to be harmless.
There are two classes of security problems: nuisances and security breaches. A nuisance attack merely prevents you from getting your work done - for example it may cause your computer to crash. Security breaches are more serious: your files could be deleted, your private data could be read, or a virus could infect your machine.
If you are the victim of a security breach, any data stored on your machine may be read or corrupted by a bad guy. If you've got important company secrets on your computer, maybe you should surf the net on another machine.
In the not-too-distant future, your computer may be able to digitally sign documents that are legally binding, just like your paper signature. Your computer may also be able to spend your money. In a world like that, security becomes even more important than it is right now.
So far, there have been no publicly reported, confirmed cases of security breaches involving Java, though there have been some suspicious events that might possibly have involved Java security problems. Of course, the lack of reported cases is no guarantee that there haven't been breaches that either weren't discovered or weren't reported. But it does indicate that breaches are rare.
You're at risk if you're running a Java-enabled browser and you visit a Web page written by a person you don't know or don't trust. Since the two most common browsers, Netscape Navigator and Microsoft Internet Explorer, are Java-enabled, most people surfing the Web are at risk.
If you maintain sensitive data on your computer that you think an unscrupulous adversary might want, you should disable Java and JavaScript, as well as not installing plug-ins, except from well-known vendors.
If you don't disable Java, think twice before visiting a Web site belonging to a person you don't know or don't trust. Of course, some people will be perfectly happy just living with the risk.
You can reduce the damage caused by a potential security breach by taking common-sense precautions like backing up your data frequently and keeping sensitive data off your Web-surfing machine.
No, they'll only help a little. Digital signatures let you know who wrote an applet, but they don't help you decide whether you can trust the author.
No. Security will always be an issue with any network software. As long as vendors are racing their products out the door and adding new functionality with each and every release, you can expect security bugs will always exist. Writing crash-proof software is hard. Writing secure software is even harder.
In our judgement, the latest versions of the two browsers offer roughly comparable levels of security.
Generally, the latest version is the safest. Be sure to regularly check your browser vendor's Web pages for announcements of new versions. Look carefully - the announcements are not always prominent.
If you use Microsoft Internet Explorer 3.0, be sure to apply Microsoft's patch which fixes a security problem.
There's a report circulating on the net, claiming to come from the USGS, containing various misleading and inflammatory statements about Java security, and using the term ``black widows.'' Some statements attributed to us in that report are simply false. You can read our original paper and see for yourself.
This is a general term for Java applets (programs) that exploit security bugs. There are some pages on the Web that demonstrate, with appropriate warning messages, some hostile applets. The applets we've seen are nuisance attacks rather than damaging attacks.
Not directly. Java can only potentially attack the browser, not the server.
Of course, you should be careful about which Java applets appear on your server. Unless you wrote the applet yourself, you don't necessarily know what it's doing. If you copy somebody else's applet, it could possibly be a trojan horse - doing something useful as well as being malicious.
Java and JavaScript, despite the similarity of their names, are not related. (Isn't marketing wonderful?) JavaScript has its own security problems, so you may also want to disable JavaScript.
This information is our opinion only. It is not the opinion of Princeton University or of our research sponsors. We do not and cannot guarantee that you will be safe if you follow our advice.
A book on this topic, Java Security: Hostile Applets, Holes and Antidotes by Gary McGraw and Edward Felten, will published by Wiley this fall.
JavaSoft has their own Frequently Asked Questions about Applet Security.
Netscape has a Netscape Navigator 2.02 Security-Related FAQ which you may find interesting. To see how they plan to evolve their security model, you may want to read Netscape's Java Security Architecture.
Mark LaDue, at Georgia Tech, has a page of hostile applets to demonstrate how serious the problem can be.
David Hopwood, at Oxford University, has also been active in breaking Java.
Microsoft doesn't (yet) have a Java security FAQ, but you may want to read their proposals for code signing (part of their Internet Development Toolbox), or maybe ``Dr. GUI Gets Webbed'', for a more whimsical look at Microsoft's vision of the Web's future.