Unauthentic "Microsoft Corporation" certificates issued by Verisign to an unidentifed person

2001-03-27T00:00:00
ID VU:869360
Type cert
Reporter CERT
Modified 2001-03-30T00:00:00

Description

Overview

On January 29 and 30, 2001, VeriSign, Inc. issued two certificates to an individual fraudulently claiming to be an employee of Microsoft Corporation. Any code signed by these certificates will appear to be legitimately signed by Microsoft when, in fact, it is not. Although users who try to run code signed with these certificates will generally be presented with a warning dialog, there will not be any obvious reason to believe that the certificate is not authentic.

Description

Microsoft released a security bulletin on March 22, 2001, describing two certificates issued by VeriSign to an individual fraudulently claiming to be an employee of Microsoft. The full text of Microsoft's security bulletin is available from their web site at

<http://www.microsoft.com/technet/security/bulletin/MS01-017.asp>

Additional information about this issue is also available from VeriSign's web site:

<http://www.verisign.com/developer/notice/authenticode/index.html>
This issue presents a security risk because even a reasonably cautious user could be deceived into trusting the bogus certificates, since they appear to be from Microsoft. Once accepted, these certificates may allow an attacker to execute malicious code on the user's system.

This problem is the result of a failure by the certificate authority to correctly authenticate the recipient of a certificate. Verisign has taken the appropriate action by revoking the certificates in question. However, this in itself is insufficient to prevent the malicious use of these certificates until a patch has been installed, because Internet Explorer does not check for such revocations automatically. Indeed, because the Certificates issued by Verisign do not contain any information regarding where to check for a revocation, Internet Explorer, or any browser, is unable to check for revocations of these certificates. Microsoft is developing an update that will enable revocation checking and install a revocation handler that compensates for the lack of information in the certificate.


Impact

Anyone with the private portions of the certificates can sign code such that it appears to have originated from Microsoft Corporation. If the user approves the execution of code signed by one of the bogus certificates, it can take any action on the system with the privileges of the user who approved the execution. The fake certificates can only be used for Authenticode signing.


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