|Test the version of Java used in this browser|
April 14, 2015: Three new versions of Java were released today: Java 7 Update 79, Java 7 Update 80 and Java 8 Update 45. These releases fix 14 security flaws. Quoting Oracle: "All of these vulnerabilities may be remotely exploitable without authentication, i.e., may be exploited over a network without the need for a username and password. "
April 14, 2015: Chrome version 42 will pour your Java coffee down the drain: Plugin blocked by default by Shaun Nichols in The Register. Chrome version 42 blocks the Java plugin by default because it uses an old deprecated plugin API. For the time being, you can tweak Chrome to run Java but that will end in September 2015.
January 21, 2015: CPU vs. PSU: According to the tech press, Oracle yesterday released Update 75 for Java version 7. This is only part of the story, as they also released Update 76 for Java 7. Update 75 is the CPU, Update 76 is the PSU. This is now a permanent thing for Oracle and Java. According to Oracle "Most users should choose the CPU release ... Java SE Patch Set Updates (PSU) contain all of fixes in the corresponding CPU, as well as additional non-critical fixes. Java PSU releases should only be used if you are being impacted by one of the additional bugs fixed in that version."
January 20, 2015: Oracle fixed 19 bugs in Java today, 13 of them were remotely exploitable. The latest versions are: Java 7 Update 75 and Java 8 Update 31. Java 7 is slated to die in April, and as part of this, the Java auto-update function will start updating version 7 installations to version 8.
October 31, 2014: I blogged about What's new with Java. Perhaps the big news here is that a "very high" security level setting for Java does not prevent unsigned applets from running. Tested on Windows 7 with both Java 7 and 8. Also, just what does it mean when the Java runtime expires.
October 14, 2014: Oracle released three new versions of Java: version 7 Update 71, version 7 Update 72 and version 8 Update 25. Also, version 8 Update 25 is now the default for new installations. Java 8 should work on Windows XP but Oracle does not officially support it.
October 14, 2014: Java version 7 is scheduled to die on April 2015.
Aug 4, 2014: Java version 7 Update 67 was released. No security related bugs were fixed. One non security bug was fixed.
July 14, 2014: It was reported that Java 7 would no longer be supported on Windows XP. This is not true, Java 7 will continue to be supported on XP. However, Java 8 will not be supported on XP.
May 29, 2014: Java version 7 Update 60 (a.k.a. version 1.7.0_60) was released. Although it contains a large number of bug fixes, none of them seem to be security related. The security baseline remains Update 55. See the Release Notes for Update 60.
May 29, 2014: The number of bugs in Java keeps increasing. According to Greg Sinclair, there were 58 Java flaws in 2010, 65 in 2011, 68 in 2012 and a whopping 208 in 2013.
Java is supported on Windows, OS X and Linux. It is not supported in iOS or Chrome OS. Java is very much involved in Android, but not in a way that is visible to end users.
Java is used both online and offline in Windows, OS X and Linux. The online use involves Java programs, typically referred to as "applets", embedded in a web page. All the security issues regarding Java involve applets. Offline, Java is used by applications installed in your operating system. Examples of these applications are below in the "Do you need Java" section. The topic of Java being used in a web browser vs. an installed application was addressed by Steve Gibson on the Jan 16, 2013 edition of his Security Now podcast (do a find for "Jared").
A component of Java has to be installed on a computer before Java programs can execute, either online or offline. This component has a couple names. It was initially referred to as the Java Virtual Machine (JVM), but now the more common term is JRE (Java Runtime Environment). Sometimes, it is just referred to as Java, which is a big misnomer as there are many parts to the Java ecosystem.
The latest edition of Java is version 7. It comes from Oracle and is supported on Windows, OS X and Linux. Oracle gave up issuing bug fixes for Java version 6 in the middle of 2013 (for free that is; you can pay Oracle for Java 6 bug fixes). Apple continues to issues bug fixes for Java 6 on Snow Leopard, Lion and Mountain Lion.
On Windows, the Java runtime (JRE) may or may not be pre-installed, the decision is left up to the hardware manufacturer. A Java version 6 runtime was pre-installed by Apple on OS X Leopard and Snow Leopard, but starting with Lion, Apple stopped pre-installing Java. Java 6 can be installed on Lion and Mountain Lion, but it will not run applets. Java 7 can be installed on Lion and Mountain Lion to run applets. Java 7 can not be installed on Snow Leopard. Lion and Mountain can have both Java 6 and Java 7 installed concurrently.
The Java runtime (JRE) on Windows comes from Oracle (previously from Sun). On OS X, Apple supplies the JRE for Java version 6, while Oracle supplies the JRE for Java version 7. Oracle is the official supplier of the JRE for Linux, but there are also other sources available. Microsoft used to maintain their own JRE on Windows but that fell by the wayside long ago. In the old days Netscape had their own JRE as did IBM and others.
Just because a Java runtime is installed, does not mean that a web browser will actually use it. There are three possible reasons for this:
Currently Java has a poor reputation for an endless stream of security flaws. But well before this, Apple and Microsoft did not like Java because it made their operating systems less important. A Java program can, in theory, run equally well on Windows, OS X and Linux. And, that's just for starters. As long as there is a JRE for an operating system, Java programs can run on that system. This opens up other environments too, such as IBM mainframes and Unix. The popular phrase, in the early days of Java was "write once, run anywhere". But, it all went wrong, well before security flaws became the main Java story.
As it played out over the years, Flash beat out Java in the marketplace on the client side (your computer). Flash served the same cross platform needs that Java was intended for. There were annoying differences between Java runtimes from different vendors which led to the sarcastic phrase "write once, debug everywhere." It may be that Flash won out simply because there was only one source (Adobe now, Macromedia initially) for its runtime environment. On the server side however, Java has always been popular.
Java programs are prepared for execution in the JVM/JRE by being translated into something called Java bytecode. The Java Runtime Environment doesn't really care about, or deal with, the Java programming language, it takes Java bytecode as input. This, along with assorted advantages to using a JVM, has led to other programming languages also being translated into Java bytecode so that they can be run in a Java Virtual Machine. In Sept. 2013 Wired reported on two such popular languages, Clojure and Scala. A version of Ruby known as JRuby also runs in a JVM. Wired reported that Twitter runs entirely inside JVMs mostly using software written in Scala but also some written in Java. LinkedIn is also married to JVMs and uses a mixture of Java and Scala.
Now that security flaws are the big issue with Java, the safest best practice is to un-install Java and see if anything breaks. I say this because, as far as I know, there is no inventory function that reports on Java usage system-wide. Since all the security issues have been with Java applets embedded in web pages, someone that only needs Java for installed applications, should disable its use in all browsers using a security feature first introduced in Java 7 Update 10 (see Oracle"s instructions). Someone needing to run Java applets should normally use a web browser that has Java disabled and use a second browser, with Java enabled, exclusively on the site(s) that need Java. If you are not sure which sites use Java, Google's Chrome browser is your friend, as it warns before running Java applets.
The Version page of this site verifies that a browser is capable of running Java applets in web pages by running a very simple applet that displays the version of Java. It also has a history of Java releases and instructions for disabling Java in assorted browsers. The source code for the applet is on the About page.
Java applets can, optionally, be digitally signed. Those that are not, started generating a new pop-up warning with the introduction of Java 7 Update 11. The "version" applet on this site is not signed. Neither are those from Oracle that test if Java is working (here and here).
Finally, you may see Oracle mention the Java security baseline. This refers to the latest version of Java that contains no security flaws. This is not necessarily the latest version. There is a different security baseline edition for Java 6 and 7. To illustrate, as of mid-January 2013, Update 37 was the security baseline edition for Java 6. Windows users had access to Update 38 which contained bug fixes, but no security related bug fixes. Apple did not produce an Update 38 for the Mac, they maxed out at Update 37.
In April 2012, Ed Bott adressed this by listing some applications and websites that require Java. See How big a security risk is Java? Can you really quit using it?. Some omissions from the article are
On the other hand are web sites that have walked away from Java:
In the beginning, Java programs embedded in web pages were called applets. That's the term I use on this site because it was created long ago. Now however, things are more complicated. According to Oracle, Java programs running inside a browser "includes plugin applets, Java Web Start applications, embedded JavaFX applications, and access to the native deployment toolkit plugins".
Windows users may find the term applet used to describe the small applications in the Control Panel (Power Options, Mouse options, Administrative Tools, etc.). These control panel thingies have nothing to do with Java, other than the Java one, which is referred to as the Java Control Panel.
Java applets can be digitally signed. Those that are not are referred to as "unsigned", "untrusted" and "sandboxed".