III. Solution
Apply a Patch from Your Vendor
Microsoft has released an update to correct this vulnerability.
The patch is described in more detail in the Microsoft security
bulletin at
-
http://www.microsoft.com/technet/security/bulletin/MS01-017.asp
Check "Microsoft Corporation" Certificates
You can identify the fake certificates by checking the validity
dates and serial numbers of the certificates. When prompted to
authorize the execution of code signed by "Microsoft Corporation",
press the "More Info" button to obtain additional information about
the certificate used to sign the code.
The fake certificates have the following description:
-
Issued to: Microsoft Corporation
Issued by: VeriSign Commercial Software Publishers CA
Valid from 1/29/2001 to 1/30/2002
Serial number is 1B51 90F7 3724 399C 9254 CD42 4637 996A
Issued to: Microsoft Corporation
Issued by: VeriSign Commercial Software Publishers CA
Valid from 1/30/2001 to 1/31/2002
Serial number is 750E 40FF 97F0 47ED F556 C708 4EB1 ABFD
No legitimate certificates were issued to Microsoft between January
29 and 30, 2001. Certificates with these initial validity dates or
serial numbers should not be authorized to execute code.
The certificate revocation list for the fake certificates can be
found at
-
http://crl.verisign.com/Class3SoftwarePublishers.crl