[<prev] [next>] [day] [month] [year] [list]
Message-ID: <871080DEC5874D41B4E3AFC5C400611E03F60BC1@UTDEVS02.campus.ad.utdallas.edu>
From: pauls at utdallas.edu (Schmehl, Paul L)
Subject: RE: Probable new MS DCOM RPC worm for Windo ws
> -----Original Message-----
> From: Ferris, Robin [mailto:R.Ferris@...ier.ac.uk]
> Sent: Friday, September 26, 2003 8:37 AM
> To: 'full-disclosure@...ts.netsys.com'
> Subject: RE: [Full-Disclosure] RE: Probable new MS DCOM RPC
> worm for Windo ws
>
> I have not yet verified if the files were installed or not
> and thats a very good point. I didnt and still dont know what
> files it changed or installed for the ms03-026. What are they?
You can go into the registry and see that. Go to
HKEY_LOCAL_MACHINE\Software\Microsoft\Updates\(Your OS)\(Next SP)\(patch
in question) and you will find the filenames (and their properties) that
were replaced by the patch.
For example, on XP:
HKEY_LOCAL_MACHINE\Software\Microsoft\Updates\Windows
XP\SP2\KB824146k\Filelist\0 shows that ole32.dll was replaced by the
MS03-039 patch and it has a build checksum of 1248ac, a build date of
Mon Aug 25 13:53:42 2003 and a version number of 5.1.2600.1263 and it's
located in C:\WINDOWS\System32.
You can then go to that directory and check the file properties to
verify that it matches what's in the registry.
Just FYI, the two other files that were replaced are rpcrt4.dll and
rpcss.dll. MS03-026 replaced the same three files.
Paul Schmehl (pauls@...allas.edu)
Adjunct Information Security Officer
The University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/~pauls/
Powered by blists - more mailing lists