Secunia CSI7
Advisories
Research
Forums
Create Profile
Our Commitment
PSI
PSI API
CSI
OSI
xSI
Vulnerabilities
Programs
Open Discussions
My Threads
Create Thread
Statistics
About

Forum Thread: Google Chrome udate

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:
OSI

This thread has been marked as resolved.
steve35 Google Chrome udate
Member 13th Nov, 2010 16:28
Ranking: 0
Posts: 2
User Since: 12th Nov, 2010
System Score: N/A
Location: HU
At present I use Windows7 and Google Chrome 7.o517.44.The OSI reveals 7.0517.41 as an insecure program.It marks all other programs secure except Google Chrome.Why?

Post "RE: Google Chrome udate" has been selected as an answer.
steve35 RE: Google Chrome update
Member 13th Nov, 2010 16:30
Score: 0
Posts: 2
User Since: 12th Nov 2010
System Score: N/A
Location: HU
udate corrected
Was this reply relevant?
+0
-0
mogs RE: Google Chrome udate
Expert Contributor 13th Nov, 2010 16:34
Score: 2265
Posts: 6,266
User Since: 22nd Apr 2009
System Score: 100%
Location: UK
Hello.
You need to remove the older file/version which Chrome leaves behind at update. Secunia continues to detect even if still in the Recycle bin.
Hope this helps....regards,

--
Was this reply relevant?
+2
-0
TiMow RE: Google Chrome udate
Dedicated Contributor 13th Nov, 2010 16:40
Score: 737
Posts: 728
User Since: 26th Jun 2009
System Score: N/A
Location: CH
When you updated Chrome to 7.0.517.44 it created a new file.
The old Chrome file (7.0.517.41) still remains and is flagged as insecure.
You need to manually delete this.

Navigate to the file location, using Windows Explorer - I can't give you the location for W7 (it should be given by the OSI scan result), but on my XP it is here (and may be similar for W7):

C:\Documents and Settings\<usename>\Local Settings\Application Data\Google\Chrome\Application\7.0.517.44\chrome.d ll

Once at the location right click the old file version number (7.0.517.41) and delete.
You should further delete this from recycle bin, to fully clear the insecurity.

You can choose whether to run a new scan or not, to check that the insecurity is gone.

TiMow

--
Computing is not yet a perfect science - it still requires humans.
Was this reply relevant?
+4
-1

This thread has been marked as locked.


 Products Solutions Customers Partner Resources Company
 
 Corporate
Vulnerability Intelligence Manager (VIM)
Corporate Software Inspector (CSI)
Consumer
Personal Software Inspector (PSI)
Online Software Inspector (OSI)
 Industry
Compliance
Technology
Integration
 Customers
Testimonials
 VARS
MSSP
Technology Partners
References
 Reports
Webinars
Events
 About us
Careers
Memberships
Newsroom


 
© 2002-2014 Secunia ApS - Rued Langgaards Vej 8, 4th floor, DK-2300 Copenhagen, Denmark - +45 7020 5144
Terms & Conditions and Copyright - Privacy - Report Vulnerability