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: PSI identifies vulnerable file that doesn't exist

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

Relating to this vendor:
Google
And, this specific program:
Google Chrome 4.x

This thread has been marked as locked.
Sizou PSI identifies vulnerable file that doesn't exist
Member 30th Mar, 2010 21:03
Ranking: 6
Posts: 7
User Since: 7th Sep, 2009
System Score: N/A
Location: N/A
I'm seeing some weird behavior from PSI that I haven't seen before. The particular issue comes up regarding Google Chrome, but I haven't seen any other Chrome users report it.

Upon completing a scan, PSI reports that I have a file, [path]\4.0.249.89\chrome.dll, that needs to be updated. ("[path]" doesn't actually appear, it's the lengthy actual path that appears.)

Here's the problem: Neither that folder nor that file exist on my computer. I deleted the folder some time ago. I can see all my hidden files and folders, and these aren't there anymore. I can't even find them from the command line (returns a "path not found" error).

I have also installed the latest version of Chrome from Google's site. Doesn't help.

Anyone have any ideas?

mogs RE: PSI identifies vulnerable file that doesn't exist
Expert Contributor 30th Mar, 2010 22:42
Score: 2265
Posts: 6,266
User Since: 22nd Apr 2009
System Score: 100%
Location: UK
Hello.
Are you really saying that you've followed the file path thro' and there's nothing at the end of it ?

--
Was this reply relevant?
+0
-0
Sizou RE: PSI identifies vulnerable file that doesn't exist
Member 31st Mar, 2010 01:07
Score: 6
Posts: 7
User Since: 7th Sep 2009
System Score: N/A
Location: N/A
Last edited on 31st Mar, 2010 01:12
The directory at the end of the path doesn't exist; I don't know what you mean by "there's nothing at the end of it." There is another directory at the end of the path, but it's the directory for the current version of Chrome, not the 4.0.249.89 version.

Since the directory doesn't exist, the file chrome.dll that is supposedly inside the directory also doesn't exist. But PSI "finds" anyway and reports it as a vulnerability.
Was this reply relevant?
+0
-0
This user no longer exists RE: PSI identifies vulnerable file that doesn't exist
Member 31st Mar, 2010 09:09
Hi,

If the file is deleted, the PSI won't pick it up when scanning. The PSI doesn't "remember" your installed applications if it can't locate them after a rescan. Try using the "open folder" folder (after expanding the entry) to get to the folder.
Also, please check the field "Installation Path" to see if this might be a backed up version of the file you deleted, or something similar.

hope this helps.
Was this reply relevant?
+0
-0

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
 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 - Disclaimer