Plugin Check Indicating QuickTime Plug-in 7.6.3 is "Outdated"



8 years ago
5 months ago


(Reporter: shinethebrightlight, Assigned: kev)





(3 attachments)



8 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: Gecko/20100401 Firefox/3.6.3


Plugin Check (i.e. 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 ->

Reproducible: Always

Steps to Reproduce:
1. Go to
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

Comment 2

8 years ago
(In reply to comment #0)
@shinethebrightlight thanks for the bug report. Can you go to, scroll down to (all the) Quicktimes and post a screenshot here.

Comment 3

8 years ago
Created attachment 446890 [details]


8 years ago
Attachment #446890 - Attachment description: Peridies_QuickTimeX → Perfidies_QuickTimeX

Comment 4

8 years ago
Created attachment 446891 [details]

Comment 5

8 years ago
(In reply to comment #2)
> (In reply to comment #0)
> @shinethebrightlight thanks for the bug report. Can you go to
>, 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 and the other a screenshot of the Mozilla Plugin Check site,



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?
Ever confirmed: true
Assignee: nobody → rdoherty

Comment 6

8 years ago
I am experiencing this same problem.

Comment 7

8 years ago
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.

Comment 8

7 years ago
In the current version of Firefox 3.6.16's plugin checker at, 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.


7 years ago
Assignee: ryan.doherty → kev

Comment 9

5 months ago
This was resolved at the time, and never updated here.
Last Resolved: 5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.