|wmccown||Foxit Reader Threat|
|20th Nov, 2009 20:36|
User Since: 26th Jun, 2009
System Score: N/A
Last edited on 20th Nov, 2009 20:39
No matter how many times I update from the "at risk" version to the latest "safe" version, Secunia PCI doesn't recognize the "safe version".
The at risk version was 3.0.2009.1817 and the patch (secured via Secunia PSI) is 220.127.116.110. I have gone through this every day for the last three days but Secunia PSI is oblivious to the update.
Foxit Reader itself says I have the update and Belarc Adviser says I have the update. That is two to one that agree that Secunia PSI is wrong!
I am using Vista Home Premium Edition, IE8 browser and take warnings seriously. This is not the first or only program update that Secunia PSI has been slow to recognize. I never see the program file path. I do not have Firefox at all. As previously stated, I have rescanned my PC several times to get Secunia PSI to recognize each iteration.
|Maurice Joyce||RE: Foxit Reader Threat|
|20th Nov, 2009 21:43|
User Since: 4th Jan 2009
System Score: N/A
Last edited on 21st Nov, 2009 00:21
|Secunia is 100% correct. It is a vulnerability checker NOT a general updater.
Version 3.0.1506 had the vulnerability.
Version 3.0.1817 fixed it.
All the releases since have been cosmetic or bug fixes.
Details are here:
Change log details for Foxit are here:
@MOGS has hit on a good point below. I would strongly advise U also switch from OSI, which only monitors a few programmes, to PSI Advanced Mode where U will get the full benefits of vulnerability checking.
Windows 7 SP1 64 Bit OS
HP Intel Pentium i7
IE 11 for Windows 7 SP1
|mogs||RE: Foxit Reader Threat|
|20th Nov, 2009 21:44|
User Since: 22nd Apr 2009
System Score: 100%
Last edited on 20th Nov, 2009 21:47
|Firstly; are you using Secunia in Advanced mode ? You would gain more information if you were to do so.
I have Foxit reader....my first, and the latest version; so I havn't as yet, had any experience of updating this particular prog. I suspect, however, that what Secunia may still be detecting is the old file/prog, in your case.
If you click on the + sign alongside the insecure entry, it will expand to reveal further info: tech. details so on and so forth. By clicking on Tech. details you will find confirmation of the file path,which you can follow, to delete if need be.
Best follow Maurice's advice!!!!
Not a customer already?
Learn more about how our market leading Vulnerability Management solutions can help you manage risk and ensure compliance.