Firefox Developer (Aurora) 2014-12-11 In add-ons manager -> Plugins, Shockwave Flash 220.127.116.11 has the alert header "Shockwave Flash is known to be vulnerable and should be updated. Update Now". Clicking on the "Update Now" link takes one to https://blocklist.addons.mozilla.org/en-US/firefox/blocked/p80 - which is the page for "Java Plugin has been blocked for your protection" In Firefox 34, the same link takes one to https://blocklist.addons.mozilla.org/en-US/firefox/blocked/p178, which is "Flash Player Plugin between 11.0 and 11.7.700.169 (click-to-play) has been blocked for your protection." - closer, but still the wrong version and no option to update. Currently installed plugins: (ask to activate:) -OpenH264 -Java Platform SE -Shockwave Flash (never activate:) -Adobe Acrobat -AdobeAAMDetect -Java Deployment Toolkit
Additional information. With a new profile, the alert above the individual plugin does not appear, instead only the header above all, "check to see if your plugins are up to date" appears (which takes one to the "plugin check & updates" page). Reverting back to the previous user profile, even with all extensions disabled, the alert inside Flash plugin block itself "Shockwave Flash is known to be vulnerable and should be updated. Update Now" reappears.
I'm seeing the same thing, running Flash 18.104.22.168, FF 34.0.5 https://i.imgur.com/8Mfeb8y.png Takes you to: https://blocklist.addons.mozilla.org/en-US/firefox/blocked/p178 Presume it should point to: https://blocklist.addons.mozilla.org/en-US/firefox/blocked/p794
Actually, scratch that, a link labeled "Update Now" should either start an update download or take me to a page where an update is available for download which https://blocklist.addons.mozilla.org/en-US/firefox/blocked/p794 does not have.
In bug 873093 we added a infoURL field to the blocklist (at least for Flash and Java). In bug 1038145 we started to use this in other parts of the plugin UI. We should start to use it here too, if present. Also, we may be picking up the wrong blocklist entry here (comment 2 looks like we're not hitting the newest applicable blocklist entry). (The notes plugincheck don't really belong here)
This looks like bug 1129287.