Recent answers to plugin check not workinghttps://support.mozilla.org/en-US/questions/9910632014-06-11T01:58:01-07:00richlaughlin, You asked, If it is blocklisted, shouldn't Firefox be flagging it up when it runs p2014-06-11T01:58:01-07:00AliceWymanhttps://support.mozilla.org/en-US/questions/991063?page=3#answer-589369<p>richlaughlin, You asked, <em>If it is blocklisted, shouldn't Firefox be flagging it up when it runs plugin check?</em>
</p><p>Good question but I think you should ask it in the PluginCheck bug you filed.
</p>If it is blocklisted, shouldn't Firefox be flagging it up when it runs plugin check?
For example, I2014-06-11T01:45:26-07:00richlaughlinhttps://support.mozilla.org/en-US/questions/991063?page=3#answer-589358<p>If it is blocklisted, shouldn't Firefox be flagging it up when it runs plugin check?
</p><p>For example, I have a Java Development Toolkit plugin which flags up "Firefox has prevented the unsafe plugin '"Java Development Toolkit' from running on <a href="http://www.mozilla.org" rel="nofollow">www.mozilla.org</a>"
</p><p>Having re-checked, this plugin is already disabled on my machine, but i think the bug report should still exist as it is still a false "update now" to a dead link.
</p>P.S. More here on Viewpoint's MetaStream 3 plugin:
http://www.currentversionplugin.info/metastream-2014-06-11T01:35:07-07:00AliceWymanhttps://support.mozilla.org/en-US/questions/991063?page=3#answer-589353<p>P.S. More here on Viewpoint's MetaStream 3 plugin:
</p><p><a href="http://www.currentversionplugin.info/metastream-3-plugin/current-version-plugin-metastream-3-plugin-38.html" rel="nofollow">http://www.currentversionplugin.info/metastream-3-plugin/current-version-plugin-metastream-3-plugin-38.html</a>
</p><p><a href="/questions/753880" rel="nofollow">/questions/753880</a> metastream 3 plugin 3.5.0.36 has been disabled due to security or stability issues, what do we do?
</p><p>See also:
<a href="/questions/976775" rel="nofollow">/questions/976775</a> Why is Metastream plug-in listed when I do a Plug-in Check on what plugins are up to date, I thought it was blocked?
</p>You wrote the following in bug 1023889
MetaStream 3 Plugin reported Viewpoint Plugin vulnerable 3.2.2014-06-11T01:22:03-07:00AliceWymanhttps://support.mozilla.org/en-US/questions/991063?page=3#answer-589348<p>You wrote the following in bug <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1023889" rel="nofollow">1023889</a>
</p><pre>MetaStream 3 Plugin reported Viewpoint Plugin vulnerable 3.2.2.26 "Update Now". When i clicked "update now" it went to a dead link <a href="http://www.viewpoint.com/technologies/viewpoint-media-player.shtml" rel="nofollow">http://www.viewpoint.com/technologies/viewpoint-media-player.shtml</a>
</pre>
<p>I vaguely remembered reading someing on that plugin so I did a google search and found the following:
<a href="https://addons.mozilla.org/en-US/firefox/blocked/p32" rel="nofollow">https://addons.mozilla.org/en-US/firefox/blocked/p32</a> Viewpoint has been blocked for your protection.
...which links to:
<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=539282" rel="nofollow">Bug 539282</a> - Blocklist the viewpoint plugin
</p><p>I would remove (or disable) that plugin and uninstall the Viewpoint Media Player program from your computer based on the above and this wikipedia article:
</p>
<ul><li><a href="http://en.wikipedia.org/wiki/Viewpoint_Media_Player" rel="nofollow">http://en.wikipedia.org/wiki/Viewpoint_Media_Player</a>
</li></ul>I have also created a bug report for the vulnerable plugin with an 'update now' dead link #1023889
2014-06-11T00:36:56-07:00richlaughlinhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-589330<p>I have also created a bug report for the vulnerable plugin with an 'update now' dead link #1023889
</p>I updated the bugs you filed, 1023835 (on Java) and 1023838 (on Flash). Thanks so much for filing 2014-06-10T23:18:36-07:00AliceWymanhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-589309<p>I updated the bugs you filed, <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1023835" rel="nofollow">1023835</a> (on Java) and <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1023838" rel="nofollow">1023838</a> (on Flash). Thanks so much for filing them!
</p>I have created bug reports 1023835 and 1033838 to go with the two already created and voted on all. 2014-06-10T22:35:17-07:00richlaughlinhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-589299<p>I have created bug reports 1023835 and 1033838 to go with the two already created and voted on all.
</p><p>Yes i agree the Adobe Acrobat plugin bug is new in Firefox 30.
</p>You can vote for the bug by clicking the "vote" link as shown in the screenshot I've attached.
By th2014-06-10T22:27:26-07:00AliceWymanhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-589296<p>You can vote for the bug by clicking the "vote" link as shown in the screenshot I've attached.
</p><p>By the way, the Adobe Acrobat plugin bug is new in Firefox 30. I don't see it in Firefox 29.0.1 (I have both Fx 29.0.1 and Fx30 installed on my Windows 7 computer, in different folders)
</p><p>The Adobe Flash plugin detection problem, where Flash 13.0.0.214 is seen as up-to-date on he PluginCheck webpage, is the same for me in Firefox 29.0.1 and Firefox 30. I'm sure that will be updated soon since Adobe's Flash Player security bulletin was just released yesterday.
</p>how do i vote for a bug?
2014-06-10T22:16:26-07:00richlaughlinhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-589291<p>how do i vote for a bug?
</p>ok i'll keep an eye on those 2 bug reports and attempt to add one for the up-to-date being falsely r2014-06-10T22:14:15-07:00richlaughlinhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-589290<p>ok i'll keep an eye on those 2 bug reports and attempt to add one for the up-to-date being falsely reported.
</p><p>regarding the Adobe Flash Player, that is a different bug again if a vulnerable plugin is not being reported as opposed to the java one which is not vulnerable but just out-of-date - i'll try to add one for that too
</p>P.S. Regarding your last comment, My Adobe Flash Player -Shockwave Flash is reporting up-to-date at2014-06-10T21:42:16-07:00AliceWymanhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-589283<p>P.S. Regarding your last comment, <em>My Adobe Flash Player -Shockwave Flash is reporting up-to-date at version 13.0.0.214, yet when i hit the up-to-date green button, Adobe Flash Player is at Version 14.0.0.125. which is a major version behind, even if the old version is not perceived as vulnerable.</em>
</p><p>Adobe Flash Player version 13.0.0.214 IS vulnerable and you should update to version 14.0.0.125 - see Adobe's security bulletin:
</p><p><a href="http://helpx.adobe.com/security/products/flash-player/apsb14-16.html" rel="nofollow">http://helpx.adobe.com/security/products/flash-player/apsb14-16.html</a>
Security updates available for Adobe Flash Player
Release date: June 10, 2014
</p>richlaughlin,
I checked the list of open PluginCheck bugs and I see that two bug reports were just2014-06-10T21:27:29-07:00AliceWymanhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-589280<p><strong>richlaughlin,</strong>
I checked the list of <a href="https://bugzilla.mozilla.org/buglist.cgi?component=plugins.mozilla.org&amp;product=Websites&amp;bug_status=__open__&amp;list_id=10463404" rel="nofollow">open PluginCheck bugs</a> and I see that two bug reports were just filed about the PluginCheck /Firefox 30 /Adobe Acrobat issue. (Please don't add comments to bug reports unless you have something constructive to add - see <a href="https://bugzilla.mozilla.org/page.cgi?id=etiquette.html" rel="nofollow">Bugzilla Etiquette</a>):
</p>
<ul><li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1023653" rel="nofollow">Bug 1023653</a> - Adobe Acrobat plugin on Windows detected as Mac, can't update
</li><li><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1023718" rel="nofollow">Bug 1023718</a> - Plugin checker for newly installed FF 30.0 shows Adobe Acrobat plugin "vulnerable" but update button just reloads plugin checker
</li></ul>
<p>You can follow those bugs by "voting" for them. It's very likely that the other PluginCheck bugs you noticed will be reported, now that Firefox 30 is out. You could file a new bug report yourself on the other PluginCheck issues, like I mentioned earlier, if you wish.
</p>..and finally. I can report that the up-to-date issue with the Java plugin is not specific to Java, 2014-06-10T20:26:43-07:00richlaughlinhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-589269<p>..and finally. I can report that the up-to-date issue with the Java plugin is not specific to Java, it happens with other plugins.
</p><p>My Adobe Flash Player -Shockwave Flash is reporting up-to-date at version 13.0.0.214, yet when i hit the up-to-date green button, Adobe Flash Player is at Version 14.0.0.125. which is a major version behind, even if the old version is not perceived as vulnerable.
</p>And on my XP machine i report a 3rd fault with plugin check. It is reporting a vulnerable plugin and2014-06-10T20:22:25-07:00richlaughlinhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-589268<p>And on my XP machine i report a 3rd fault with plugin check. It is reporting a vulnerable plugin and the Update Now link is dead.
</p><p>MetaStream 3 PluginnpViewpoint Plugin vulnerable
3.2.2.26
Update Now
</p><p><a href="http://www.viewpoint.com/technologies/viewpoint-media-player.shtml" rel="nofollow">http://www.viewpoint.com/technologies/viewpoint-media-player.shtml</a>
not found
</p><p>thanks ...
</p>I now have Firefox 30 and the fault still exists - it is still telling me v55 is up to date when v602014-06-10T07:56:55-07:00richlaughlinhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-589021<p>I now have Firefox 30 and the fault still exists - it is still telling me v55 is up to date when v60 is available
</p><p>In fact there is another fault. It is telling me my Adobe Acrobat NPAPI Plug-inAdobe Acrobat NPAPI Plug-in is vulnerable (11.0.7.79 Update Now) but when i click on update now it just reloads the plugin check.
</p>ok, thank you.
2014-06-08T23:53:53-07:00richlaughlinhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-588332<p>ok, thank you.
</p>richlaughlin, I would wait until you've updated to Firefox 30 (which should be released very soon) a2014-06-08T23:20:11-07:00AliceWymanhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-588316<p><strong>richlaughlin,</strong> I would wait until you've updated to Firefox 30 (which should be released very soon) and then post back. The PluginCheck website is being reworked for Firefox 30 and that might make a difference in your results (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=956905#c136" rel="nofollow">ref</a>.)
</p>Yes the bug is that it is showing a plugin as up-to-date (java v55) when it isn't (java v60 availabl2014-06-08T22:47:02-07:00richlaughlinhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-588303<p>Yes the bug is that it is showing a plugin as up-to-date (java v55) when it isn't (java v60 available). I don't know if it's specifically the Java one that only has the problem as it is the only one i've found to be showing incorrectly. i did read about the bug report that was referred to by guigs2 but it appeared to be about a different issue so i wondered if someone was looking at the one i found.
</p>You wrote, Bug still occurring - did you get a reply from a Mozilla employee?
guigs2 is a Mozilla (H2014-06-08T21:55:43-07:00AliceWymanhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-588297<p>You wrote, <em>Bug still occurring - did you get a reply from a Mozilla employee?</em>
</p><p><strong>guigs2</strong> is a Mozilla (Helpdesk) employee. I don't know if she is going to reply further but, here's my take on this:
</p><p><strong>guigs2</strong> referred to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1008387" rel="nofollow">Bug 1008387</a> <em>- Java Deployment Toolkit is labeled as known to be vulnerable. Use with caution.</em> That bug is still open, and is about the <strong>Java Deployment Toolkit</strong> plugin being shown as "vulnerable" in the Add-ons Manager but not on the <a href="http://www.mozilla.org/en-US/plugincheck/" rel="nofollow">PluginCheck</a> page. I keep the Java Deployment Toolkit plugin set to "Never Activate" (disabled) in the Add-ons Manager Plugins list, so it doesn't show up on the Mozilla PluginCheck page. The Deployment Toolkit plugin doesn't need to be enabled - see <a href="http://kb.mozillazine.org/Java#Java_Deployment_Toolkit_plugin" rel="nofollow">http://kb.mozillazine.org/Java#Java_Deployment_Toolkit_plugin</a> ... which links to <a href="http://www.java.com/en/download/faq/deployment_toolkit.xml" rel="nofollow">http://www.java.com/en/download/faq/deployment_toolkit.xml</a>
</p><p>Are you asking why <strong>Java(TM) Platform SE 7 U55</strong> Next Generation Java Plug-in (Java 7 Update 55) is still being shown as up-to-date on the Mozilla <a href="http://www.mozilla.org/en-US/plugincheck/" rel="nofollow">PluginCheck</a> page, when Java 7 Update 60 is the latest version? Or is your question more general: why can't PluginCheck be kept updated?
</p><p>Java 7 Update 60 isn't a security release, like I mentioned before. Just a GUESS but maybe that's why no one has filed a bug report? I really don't know. Anyway, I don't think this is anything that Mozilla Support can answer. The best I can suggest is to submit feedback to <a href="http://input.mozilla.org/feedback" rel="nofollow">input.mozilla.org/feedback</a> or file a new bug report at <a href="http://bugzilla.mozilla.org" rel="nofollow">bugzilla.mozilla.org</a> under the Websites - plugins.mozilla<em>.</em>org component (you can use
<a href="https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&amp;component=plugins.mozilla.org" rel="nofollow">this form</a> after registering at bugzilla).
</p>Bug still occurring - did you get a reply from a Mozilla employee?
2014-06-08T18:43:26-07:00richlaughlinhttps://support.mozilla.org/en-US/questions/991063?page=2#answer-588268<p>Bug still occurring - did you get a reply from a Mozilla employee?
</p>