Java Deployment Toolkit 184.108.40.206 plug-in is blocked. I now cannot view media on certain pages. Is there a fix?
Java Deployment Toolkit 220.127.116.11 plug-in is blocked. It is still enabled, but FF is blocking it all the same. I now cannot view media on certain pages. Is there a fix? Are you going to offer a secure replacement?
Please check if all your plugins are up-to-date. To do this, go to the Mozilla Plugin Check site.
Once you're there, the site will check if all your plugins have the latest versions. If you see plugins in the list that have a yellow Update button or a red Update now button, please update these immediately.
To do so, please click each red or yellow button. Then you should see a site that allows you to download the latest version. Double-click the downloaded file to start the installation and follow the steps mentioned in the installation procedure.
Also refer to
What kind of media can you not view?
Please post a link to a page that does not require a login and describe the content on the page that you can not view. You can post a screenshot. After saving the screenshot to your hard drive, click the Browse button below the reply text box, navigate to the saved image and click it
Java Deployment Toolkit 18.104.22.168 is the most currently available version.
You should be able to view Java applets. The Deployment Toolkit is intended for those who edit Java applets or edit pages with Java applets.
Why it is being blocked (July 18, 2013) - https://addons.mozilla.org/en-US/firefox/blocked/p428
由 TheOldFox 於 修改
It shouldn't be a problem if its blocked. I think the issue is elsewhere, in particular - download the latest Flash player:
http://get.adobe.com/flashplayer/ (uncheck the box to get McAfee when downloading)
If you use extensions (Firefox/Tools > Add-ons > Extensions) that can block content (e.g. Adblock Plus, NoScript, Flash Block, Ghostery) then make sure that such extensions aren't blocking content.
I've installed the latest version of Java and FIrefox. I note the Java Deployment Kit 7.0.400.43 is both shown as (a) up to date in the plugincheck but (b) vulnerable in addons. Is this _always_ vulnerable and, if so, why is the add-on installed by default? (I just did a fresh install of Firefox after completely wiping it and it's still there.)
Yes, the Java Deployment Toolkit is always labeled as vulnerable, and is automatically set to Never Activate.
Oracle still needs to fix the vulnerabilities with that plugin.
That plugin is mainly needed by Java Developers. Average users shouldn't need that plugin for anything on the web, but some private or institutional intranets may need that plugin for certain applications. In those cases the user can select Ask to activate in the Add-ons Manager > Plugins tab
In all fairness, Java is the most annoying, piece-of-shit software on the entire internet. 99% of programs for web and filesharing need it, but it's so full of holes that swiss cheese would probably be more secure... worse, nobody wants the hassle of inventing something better.
Java is a total disgrace.
I understand the the FF team want users to be secure-by-default but I need to use this plugin and hence need this set this to always enable (As the ask to enable setting breaks JDT auto-detection)
Surely there is some way but bypass this advisory.
EDIT: Found it (Though all the help on this topic is misleading)
Click on the lock (if an SSL enabled site) icon click "more information", select the permissions tab and finally tick "Java deployment toolkit" in the "Activate plugins" section
由 SilentMobius 於 修改
Thanks SilentMobius for an answer that works! One note: you can go to Tools -> Page Info -> Permissions, you do not need to click a lock on a secure site, and then More Information. That just brings up the Page Info box on the Security tab. Hopefully Mozilla FF won't decide to remove "bad" things from that permission list entirely, to prevent enabling.
I have done all these things suggested and Java runtime environment is still blocked. The options in ADD-On manager are two: ask to activate or never activate. I selected "ask to activate" but it made no difference. Also what is strange about Add-on manager and other Firfox management oages is there is no apply button. So I assume just moving to another page records the selection? Anyway I have gone to permissions and checked allow for Java Deployment and Java JRE but when I go to Java's test page all I get is the java log with the dots going round and round and it just stays that way...the java verify version page is the same. I am a developer and need to use java rte and jdk. Any suggestions?
BTW: I have done the java JRE uninstall and reinstall many times. I even did the deep uninstall using Revo Uninstaller and then the Void Tools Search utility to make sure all remnants of java were uninstalled. Then I installed the 32-bit version of the JRE. When I go to the command line and type java -version it correctly shows java is installed (the current version) and the Java Control Panel confirms the correct path. In Microsoft IE10 browser I go to the advanced security and it shows java greyed out and indicates a check mark in front of Mozilla as the default browser for java. OK, then why doesn't Firefox run the dang thing? I have enabled the plug-in. Something is blocking it but what? Shouldn't Mozilla work with Oracle to figure this out? I have two weeks nw working in this with no solution in sight.
I'm also experiencing this problem. There are a number of very popular vendors of enterprise server, storage, and networking hardware (Dell, EMC, etc.) that use the Java Deployment Toolkit for their appliances' web interface.
由 tacmas 於 修改
I am puzzled why Mozilla and Oracle executives cannot sit down together and put a team together to cooperatively close the security problems in java and blocking tactics of Firefox so the cyber world can get on with its business of hassle-free computing without being blocked at every turn in the road when wanting to run significant software. The CEO of Oracle seems obsessed with his boat but what is the excuse of the CEO of Mozilla? Is this another symptom of our blocked society like the US Congress and the President? You know, all it takes is a phone call from someone minding the store.
... what is the excuse of the CEO of Mozilla?
She's out wrangling lizards.
Java Deployment Toolkit (click-to-play) has been blocked for your protection.
Why was it blocked?
The Java Deployment Toolkit plugin is known to be insecure and is unnecessary in most cases. Users should keep it disabled unless strictly necessary.
Who is affected?
All Firefox users who have this plugin installed.
What does this mean?
The problematic add-on or plugin will be automatically disabled and no longer usable. When Mozilla becomes aware of add-ons, plugins, or other third-party software that seriously compromises Firefox security, stability, or performance and meets certain criteria, the software may be blocked from general use. For more information, please read this support article.
That is merely copy and pasted from the URL mentioned above.
On that page is a link to see a copy of the request to block filed in Bugzilla. However, the bug is forbidden to view by the general public, so there is no real explanation with proof available to anyone.
I think that only adds to the confusion. If there is a huge vulnerability, I think it should be demonstrated, explained clearly to the users (who in this case are likely developers who could understand such things), and they should decide for themselves if it's a use-case they need to be concerned with.
If they use this feature only on a local area network, or only on the intranet, to run a business, then automatically disrupting functionality by default may cause more problems than a use case which they will not likely encounter. Then perhaps the filtering of the vulnerability from external sources would simply be an exercise for their security administrators.
After a little searching, I found this posting, which seems to be the first encounter of this bug, and resolution?
There's a specific tool to "easily" allow someone to do these things to you, from other computers on your LAN. It is unclear to me if they need Administrator rights to run this tool, or if they must be on a specific proximity to your computer i.e. your LAN or intranet or even the ISP? The most vulnerable, I think, would be corporate users (anyone with a large network, regardless if a university, non-profit, small business, or enterprise level, etc).
What is clear from this tool's README file is that the vulnerability is not limited to Firefox or Oracle's JDK. In fact, almost every commonly installed application is vulnerable. Some of the more familiar names on the list include:
So the problem is much bigger than Firefox or Java JDK. It is in fact a common failure of developers to design a secure update process. As such, I think blocking JDK in Firefox is pretty pointless. It's like using a fire extinguisher on a cigarette in the middle of a forest fire, for fear of preventing a forest fire. Just because Firefox blocked this, there's probably still a dozen or more ways for this to occur on your computer.
It's a problem developers worldwide are too lazy or stupid to address. However, saying NO to developers in a high visibility app like Firefox is definitely a powerful way to raise awareness, and force another highly visible developer's hand (Oracle) to implement update verification mechanisms.
It's too bad that Mozilla simultaneously decided to unilaterally block the application and try to hide the bug. Like an ostrich burying its head in the sand. They missed the opportunity to raise awareness of a critical issue that is larger than either Firefox or Oracle combined. It's a software design practice that needs to be updated. That can only occur by raising awareness. What is even more unforgivable, is Oracle, even after being aware for almost 3 years now, has still failed to implement and push to release (not beta), a fix.
Hopefully this post is clear, removes confusion of the issue, and is not censored by Mozilla.
With respect to Mozilla "hiding" or making specific security-related Bug reports confidential, see this:
@the-edmeister: Thanks for the URL.
Security through obscurity, really? It is my opinion that hard or soft disabling this addon gives a false sense of security, while selectively enabling it so you can work on known sites for which you are the developer poses a minimal risk.
Citing the same document:
Disclosure of security vulnerabilities
- "The security module owner, peers, and other members of the Mozilla security bug group will not be asked to sign formal nondisclosure agreements or other legal paperwork. However we do expect members of the group"
I am not part of that group. I am neither legally nor ethically nor morally bound to remain silent. The "super-secret" information is readily available on the internet within a matter of seconds.
- "Please try not to keep bugs in the security-sensitive category for an unreasonably long amount of time."
3 years is unreasonably long in my opinion.
- "Please try to be understanding and accommodating if a Mozilla distributor has a legitimate need to keep a bug in the security-sensitive category for some reasonable additional time period, e.g., to get a new release distributed to users."
Security through obscurity is not a legitimate need. 3 years is not a reasonable amount of time. There seems to be no plan on behalf of Oracle to address this, or it would have done so YEARS ago. As a result, a release does not seem likely in the foreseeable future.
- "Changing this policy
This policy is not set in stone. It is our hope that any disputes that arise over membership, disclosure, or any other issue addressed by this policy can be resolved by consensus among the Mozilla security module owner, the module owner’s peers, and other security bug group members through discussions on the private security bug group mailing list."
On this issue, they can go on pretending they have the absolute control over information. It is pure denial.
This vulnerability has nothing to do with Mozilla. It can be exploited in dozens or hundreds of other ways. It is based on an inherent weakness of insecure networking protocols and laziness or ignorance of developers and international, billion dollar corporations that develop core software used to run billions of systems. Hiding the details of this one bug report is inconsequential, as a few seconds of searching gets you all the gory details.
Someone can use this exploit technique on you even if the JDK plugin is disabled. Even if you do not have JDK installed. Even if you do not use Mozilla Firefox. Maybe this policy is more appropriate to bugs that affect ONLY Mozilla software, but NOT for general industry problems. Oh well, this entire issue is just silly now. There's nothing more to say on this thread.
I know this will fall on deaf ears, but I have to respond anyway.
I have the unfortunate responsibility to manage AIX machines. In order to do so I use IBM's HMC. The HMC *requires* firefox (won't work with IE or Chrome.) Console windows for systems managed by the HMC require java. Since firefox *helpfully* disables Java for me, I'm unable to do my job.
Seriously, which is worse? Giving me the option to enable Java when *I tell you to* or forcing me to install an older, bug ridden and vulnerable version of firefox?
The "solution" to enable java by clicking the red plugin box doesn't work because I have a grey plugin box that doesn't give that option. Digging further, I've allowed java by clicking the lock and going to "more information" and then "permissions" and allowing java there, but it ignores my requests.
Please stop "helping" me, Mozilla.