Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security NTBugtraq
[Top] [All Lists]

Problems with MS05-013

Subject: Problems with MS05-013
Date: Wed, 16 Feb 2005 13:32:28 -0600
?
As part of our patch management process, we have as part of our login scripts a 
control that verifies that various patches and hotfixes have been installed by 
checking file version numbers. I'm seeing a problem with MS05-013. According to 
the KB article for this hotfix, the updated file provided for his fix is 
dhtmled.ocx, and should be at version 6.1.0.9232. After installing the hotfix, 
I was suprised to see that our hotfix checker still tagged my computer. Lookint 
at the file properties, my version of dhtmled.ocx has a value of 6.1.0.8244. 
Clicking on the actual File Version property shows a very different 6.01.8244.
 
While it's easy for me to change the expected version number in our checker, 
I'd like to make sure that this hotfix is actually being applied and the 
correct file is being installed.

--
NTBugtraq Editor's Note:

Most viruses these days use spoofed email addresses. As such, using an 
Anti-Virus product which automatically notifies the perceived sender of a 
message it believes is infected may well cause more harm than good. Someone who 
did not actually send you a virus may receive the notification and scramble 
their support staff to find an infection which never existed in the first 
place. Suggest such notifications be disabled by whomever is responsible for 
your AV, or at least that the idea is considered.
--

<Prev in Thread] Current Thread [Next in Thread>