# Java 7 Vuln **URL:** \ **Category:** General Discussion\ **Created:** [January 14, 2013, 6:02pm UTC](https://forum.inductiveautomation.com/t/java-7-vuln/5683 "2013-01-14T18:02:06Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![jsham](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@jsham](https://forum.inductiveautomation.com/u/jsham)\ **Post date:** [January 14, 2013, 6:02pm UTC](https://forum.inductiveautomation.com/t/java-7-vuln/5683/1 "2013-01-14T18:02:06Z")
Where does the community stand on the latest Java 7 Vuln? I’m still trying to get my arms around it, but it appears to have serious consequences for systems running Ignition, both from the server and desktop interfaces. Is IA preparing a statement or some guidance regarding these issues? [http://www.kb.cert.org/vuls/id/625617](http://www.kb.cert.org/vuls/id/625617) [https://www.us-cert.gov/cas/techalerts/TA13-010A.html](https://www.us-cert.gov/cas/techalerts/TA13-010A.html) ---
**Author:** ![jsham](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@jsham](https://forum.inductiveautomation.com/u/jsham)\ **Post date:** [January 14, 2013, 6:05pm UTC](https://forum.inductiveautomation.com/t/java-7-vuln/5683/2 "2013-01-14T18:05:51Z")
I hate replying to my own post, but I wanted to add that I noticed the Firefox browser this morning is disabling the Java 7 plug-in by default right now. This sort of behavior will certainly elicit some phone calls from clients wanting us to explain if it’s safe to re-enable. Wanting to be prepared with a statement on how it impacts them… ---
**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\ **Post date:** [January 14, 2013, 6:10pm UTC](https://forum.inductiveautomation.com/t/java-7-vuln/5683/3 "2013-01-14T18:10:28Z")
We sent out a mass notice about this to all customers on Friday, and we’re sending out another today. Upgrading to Java 7u11 is highly recommended (vulnerability has been fixed). Short version: Upgrade to 7u11 and set the Java security settings to high, like so: ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/6/686651d09e3fc38464a447d4e74d05b3986e7322.png) ---
**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\ **Post date:** [January 14, 2013, 6:11pm UTC](https://forum.inductiveautomation.com/t/java-7-vuln/5683/4 "2013-01-14T18:11:15Z")
(Or “Very High” if you want: doesn’t make a difference as far as Ignition’s compatibility is concerned) ---
**Author:** ![jsham](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@jsham](https://forum.inductiveautomation.com/u/jsham)\ **Post date:** [January 14, 2013, 6:13pm UTC](https://forum.inductiveautomation.com/t/java-7-vuln/5683/5 "2013-01-14T18:13:44Z")
Carl, Thanks. I’ll look for the notice to come through my inbox. Articles like this one… [https://www.networkworld.com/community/blog/oracle-releases-emergency-java-patch-experts-warn-flaws-may-take-2-years-fix](https://www.networkworld.com/community/blog/oracle-releases-emergency-java-patch-experts-warn-flaws-may-take-2-years-fix) certainly don’t help things either! ---
**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\ **Post date:** [January 14, 2013, 6:30pm UTC](https://forum.inductiveautomation.com/t/java-7-vuln/5683/6 "2013-01-14T18:30:06Z")
No, the certainly don’t. We’re monitoring this issue. Of course, our stuff is signed, so the high or very high security setting should nicely protect you while allowing our programs to run.