User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:126.96.36.199) Gecko/20100401 Firefox/3.6.3 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:188.8.131.52) Gecko/20100401 Firefox/3.6.3 Greetings, Plugin Check (i.e. https://www.mozilla.com/en-US/plugincheck/) is indicating that the plugin for QuickTime Plug-in 7.6.3 is outdated and potentially vulnerable, but QuickTime 7 is _not_ installed on this system (i.e. QuickTime 7 is an optional install, which I did not select to install). Rather, this system only has QuickTime X (default QuickTime install for Snow Leopard). Should QuickTime X be treated as equal to QuickTime 7? Not seeing any mention from Apple of re: an updated version for QuickTime X (as of 14 May 2010; see here -> http://support.apple.com/kb/HT1222). Reproducible: Always Steps to Reproduce: 1. Go to https://www.mozilla.com/en-US/plugincheck/ 2. Plugin Check runs check on browser plug-ins 3. Review Plugin details to find possibly outdated version of Apple QuickTime plugin Actual Results: Plugin Details Status Action 1 of 3 plugins are potentially vulnerable Plugin Icon Plugin Icon QuickTime Plug-in 7.6.3 The QuickTime Plugin allows you to view a wide variety of multimedia content in web pages. For more information, visit the QuickTime Web site. Outdated Version Update Expected Results: As of right now, I am not sure what to make of QuickTime X as I am not clear if it is indeed susceptible to any and all vulnerabilities that may impact QuickTime 7 (i.e. version 7.6.3). Hoping to clarify whether this is an issue, or not.
Created attachment 445285 [details] Screenshot of what I see on Mac OS X 10.6 with Quicktime 10.0, Firefox 3.6.4
(In reply to comment #0) @shinethebrightlight thanks for the bug report. Can you go to http://ozten.com/random/perfidies/debug.html, scroll down to (all the) Quicktimes and post a screenshot here.
Attachment #446890 - Attachment description: Peridies_QuickTimeX → Perfidies_QuickTimeX
(In reply to comment #2) > (In reply to comment #0) > @shinethebrightlight thanks for the bug report. Can you go to > http://ozten.com/random/perfidies/debug.html, scroll down to (all the) > Quicktimes and post a screenshot here. As requested, following are links to two screenshots re: QuickTime (one from the site http://ozten.com/random/perfidies/debug.html and the other a screenshot of the Mozilla Plugin Check site, https://www.mozilla.com/en-US/plugincheck/): -> https://bugzilla.mozilla.org/attachment.cgi?id=446890 -> https://bugzilla.mozilla.org/attachment.cgi?id=446891 Mozilla's Plugin Check still indicates that the plugin is "outdated", but there does not appear to be any updates for QuickTime X (QuickTime Player is not installed on this system). One other strange finding...on another newly installed Mac OS X (10.6) system (i.e. installed the OS a few days ago), which also only has QuckTime X and not QuickTime Player installed, Mozilla's Plugin Check displays version 7.6.6 (i.e. current version) for the QuickTime Player plugin. It appears that there may be a discrepancy with plugin versions as the system with the "outdated" plugin had the OS installed months earlier. Wondering if any of this needs to be brought to Apple's attention?
I am experiencing this same problem.
I have verified that I have the Quicktime 7.6.6 plugin installed, but FF still reports I have 7.6.3. I recently re-installed the OS on this Mac, due to hard drive failure. This has been a problem from day 1. Btw, there is no Quicktime X plugin as of today.
In the current version of Firefox 3.6.16's plugin checker at http://www.mozilla.com/en-US/plugincheck/, Quicktime plugin version 7.6.6 is erroneously reported as outdated version 7.6.3. However, version 7.6.6 is the correct, up-to-date version for Snow Leopard systems (OS X 10.6). You should fix this because the plugin checker is a useful tool, but it wastes the time of Snow Leopard users.
This was resolved at the time, and never updated here.
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.