navigation bar left navigation bar right

Secunia CSI7
navigation left tab Advisories navigation right tab
navigation left tab Research navigation right tab
navigation left tab Forums navigation right tab
navigation left tab Create Profile navigation right tab
navigation left tab Our Commitment navigation right tab
Open Discussions
My Threads
Create Thread

Forum Thread: Chrome not updated

You are currently viewing a forum thread in the Secunia Community Forum. Please note that opinions expressed here are not of Secunia but solely reflect those of the user who wrote it.

This thread was submitted in the following forum:
PSI 2.0 Beta

This thread has been marked as resolved.
runrig Chrome not updated
Member 18th Sep, 2010 14:59
Ranking: 3
Posts: 26
User Since: 29th Aug, 2010
System Score: N/A
Location: UK
I have Google Chrome 6.0.472.62

PSI is showing 6.0.472.59 as patched

This has happened before, in fact on last Chrome update


Chrome is default browser

heaven doesn't want me, and hell is afraid I'll take over

Post "RE: Chrome not updated" has been selected as an answer.
TiMow RE: Chrome not updated
Dedicated Contributor 18th Sep, 2010 17:55
Score: 737
Posts: 728
User Since: 26th Jun 2009
System Score: N/A
Location: CH
Last edited on 18th Sep, 2010 18:06
Using PSI, I had the same as you reported - 6.0.472.59 showing as patched, and About Chrome showing 6.0.472.62.

Went to the file location in Windows Explorer to check both were present, then deleted the old file. Pop up bubble showed Chrome ...59 and Gears removed.

Re-scanned PSI - pop up bubble showed new programs of Chrome ...62 and Gears. Correct version (...62) showing in Patched and Chrome is present under Secure Browsing ( only).

Even with the differences with 2.0 beta, a rescan of PSI may do the trick, also, for you.


ADDITION: In the following Secunia Vuln. Rep. relating to insecure embedded flash plug-in in Chrome, @Kurosh has posted that this has been fixed in the latest update, correctly relaying the info. in the Chrome blog link he posted.

As of time of posting Secunia rules are not reflecting this according to Chrome listing under Secure Browsing ( - still showing as a cat. 5 threat.

Computing is not yet a perfect science - it still requires humans.
Was this reply relevant?
mogs RE: Chrome not updated
Expert Contributor 18th Sep, 2010 20:42
Score: 2265
Posts: 6,268
User Since: 22nd Apr 2009
System Score: 100%
Location: UK
This information was also posted in CYBERCLIPS 95 at 0937hrs this morning.
Tho' I've got psi 2.0 Beta installed, have neither Stable nor Beta Chrome nor Frame, so unable to comment on other findings.
I have to rely on my own memory faculties when it comes to removing old dev and canary build files !! The actual release timings are oft when I 'm out at work ! Hope this is informative.

Was this reply relevant?
This user no longer exists RE: Chrome not updated
Member 20th Sep, 2010 09:07

Our rules have been updated. If you run a full rescan, the PSI will flag any version prior to 6.0.472.62 as Insecure.

hope this helps.
Was this reply relevant?

This thread has been marked as locked.

 Products Solutions Customers Partner Resources Company
Vulnerability Intelligence Manager (VIM)
Corporate Software Inspector (CSI)
Personal Software Inspector (PSI)
Online Software Inspector (OSI)
Technology Partners
 About us

Secunia is a member of FIRST Secunia is a member of EDUcause Secunia is a member of The Open Group Secunia is a member of FS-ISAC
Secunia © 2002-2015 Secunia ApS - Rued Langgaards Vej 8, 4th floor, DK-2300 Copenhagen, Denmark - +45 7020 5144
Terms & Conditions and Copyright - Privacy - Report Vulnerability - Disclaimer
follow Secunia on Facebook follow Secunia on Twitter follow Secunia on LinkedIn follow Secunia on YouTube follow Secunia Xing follow Secunias RSS feed follow Secunia on Google+