Microsoft Security Advisory (2607712)

Why was this advisory revised September 19, 2011? 
Microsoft revised this advisory to announce the rerelease of the KB2616676 update. The rerelease is now cumulative and addresses a known issue described in Microsoft Knowledge Base Article 2616676 where the original KB2616676 update, on supported editions of Windows XP and Windows Server 2003 only, did not contain the digital certificates included in the KB2607712 and KB2524375 updates.

Customers of supported editions of Windows XP and Windows Server 2003 should apply the rereleased version of the KB2616676 update to be protected against the use of the fraudulent certificates as specified in this advisory. Customers of supported editions of Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2 are not affected by this rerelease.

Note The update will not be offered to customers of supported editions of Windows XP and Windows Server 2003 in the case where the original KB2616676, KB2607712, and KB2524375 updates have all been previously applied as the rerelease package is cumulative and contains all changes from these three update packages.

The majority of customers have automatic updating enabled and will not need to take any action because the rereleased KB2616676 update will be downloaded and installed automatically.

Is Windows Developer Preview affected by this issue? 
Yes. The KB2616676 update is available for the Windows Developer Preview release. Customers of Windows Developer Preview are encouraged to apply the update to their systems. The update is only available on Windows Update.

Why was this advisory revised September 13, 2011? 
Microsoft revised this advisory to announce the release of the KB2616676 update that addresses this issue. The update adds six additional DigiNotar root certificates that are cross signed by Entrust or GTE to the Microsoft Untrusted Certificate Store. The KB2616676 update replaces the KB2607712 update and also contains the previous five DigiNotar root certificates added to the Microsoft Untrusted Certificate Store by the KB2607712 update.

Although the KB2616676 update replaces the KB2607712 update, the KB2607712 update is not a prerequisite for the KB2616676 update. Regardless of whether or not the KB2607712 update has been applied, customers should apply the KB2616676 update to address the issue described in this advisory. Customers who apply the KB2616676 update do not need to apply the KB2607712 update.

Why was this advisory revised September 6, 2011? 
Microsoft revised this advisory to announce the release of an update that addresses this issue. The update adds five DigiNotar root certificates to the Microsoft Untrusted Certificate Store. Typically no action is required of customers to install this update, because the majority of customers have automatic updating enabled and this update will be downloaded and installed automatically. For customers who do not have automatic updating enabled, see Microsoft Knowledge Base Article 2607712 for information on how to manually apply the update.

On August 29, 2011, Microsoft removed the trust from one DigiNotar root certificate by updating the Microsoft CTL. Why is Microsoft releasing an update? 
Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2 use the Microsoft Certificate Trust List to validate the trust of a certification authority. Windows XP and Windows Server 2003 do not use the Microsoft Certificate Trust List to validate the trust of a certification authority. As a result, an update is needed for all editions of Windows XP and Windows Server 2003 to protect customers.

After the CTL update on August 29, 2011, Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2 users who accessed a Web site that was signed by an untrusted DigiNotar root certificate would be presented with a warning message indicating that the trust of the certificate could not be verified. Users were allowed to click through this warning message to access the site.

In order to protect customers more comprehensively against possible man-in-the-middle attacks, Microsoft is releasing an update that takes additional measures to protect customers by completely preventing Internet Explorer users from accessing resources of Web sites that contained certificates signed by the untrusted DigiNotar root certificates. Internet Explorer users who apply this update will be presented with an error message when trying to access a Web site that has been signed by either of the above DigiNotar root certificates. These users will not be able to continue to access the Web site.

What does the KB2616676 update do? 
On all supported releases of Microsoft Windows, the KB2616676 update adds eleven DigiNotar root certificates to the Microsoft Untrusted Certificate Store. In addition, the KB2616676 update also includes the certificates in the KB2524375 update that was released on July 6, 2011.

How will this update change the user experience when trying to access a Web site that has been encrypted with TLS and signed by an untrusted DigiNotar root certificate? 
Internet Explorer users who try to access a Web site that has been signed by an untrusted DigiNotar root certificate will be prompted with an error message. Due to the fact that this certificate is located in the Microsoft Untrusted Certificate Store, Internet Explorer will not allow users to proceed to the Web site. The Web site will remain unavailable until the Web site certificate is replaced with a new certificate that is signed by a trusted root certificate.

After applying the update, how can I verify the certificates in the Microsoft Untrusted Certificates Store? 
For information on how to view certificates, see the MSDN article, How to: View Certificates with the MMC Snap-in.

In the Certificates MMC snap-in, verify that the following certificates have been added to the Untrusted Certificates folder:

*Certificate added to the Untrusted Certificates folder by these updates.

The KB2616676 update also includes the certificates in the KB2524375 update added to the Untrusted Certificates folder.

What is the scope of the advisory? 
The purpose of this advisory is to notify customers that Microsoft has confirmed at least one fraudulent certificate has been issued by DigiNotar and is being used in active attacks. Microsoft has issued an update for all supported releases of Microsoft Windows that addresses the issue.

What is cryptography? 
Cryptography is the science of securing information by converting it between its normal, readable state (called plaintext) and one in which the data is obscured (known as ciphertext).

In all forms of cryptography, a value known as a key is used in conjunction with a procedure called a crypto algorithm to transform plaintext data into ciphertext. In the most familiar type of cryptography, secret-key cryptography, the ciphertext is transformed back into plaintext using the same key. However, in a second type of cryptography, public-key cryptography, a different key is used to transform the ciphertext back into plaintext.

What is a digital certificate? 
In public-key cryptography, one of the keys, known as the private key, must be kept secret. The other key, known as the public key, is intended to be shared with the world. However, there must be a way for the owner of the key to tell the world who the key belongs to. Digital certificates provide a way to do this. A digital certificate is a tamperproof piece of data that packages a public key together with information about it - who owns it, what it can be used for, when it expires, and so forth.

What are certificates used for? 
Certificates are used primarily to verify the identity of a person or device, authenticate a service, or encrypt files. Normally you won’t have to think about certificates at all. You might, however, see a message telling you that a certificate is expired or invalid. In those cases you should follow the instructions in the message.

What is a certification authority (CA)? 
Certification authorities are the organizations that issue certificates. They establish and verify the authenticity of public keys that belong to people or other certification authorities, and they verify the identity of a person or organization that asks for a certificate.

What is a Certificate Trust List (CTL)? 
A trust must exist between the recipient of a signed message and the signer of the message. One method of establishing this trust is through a certificate, an electronic document verifying that entities or persons are who they claim to be. A certificate is issued to an entity by a third party that is trusted by both of the other parties. So, each recipient of a signed message decides if the issuer of the signer's certificate is trustworthy. CryptoAPI has implemented a methodology to allow application developers to create applications that automatically verify certificates against a predefined list of trusted certificates or roots. This list of trusted entities (called subjects) is called a certificate trust list (CTL). For more information, please see the MSDN article, Certificate Trust Verification.

What caused the issue? 
Microsoft is aware of active attacks using at least one fraudulent digital certificate issued by DigiNotar, a certification authority present in the Trusted Root Certification Authorities Store. A fraudulent certificate could be used to spoof content, perform phishing attacks, or perform man-in-the-middle attacks against all Web browser users including users of Internet Explorer. While this is not a vulnerability in a Microsoft product, this issue affects all supported releases of Microsoft Windows.

What might an attacker use the vulnerability to do? 
An attacker could use these certificates to spoof content, perform phishing attacks, or perform man-in-the-middle attacks against all Web browser users including users of Internet Explorer.

What is a man-in-the-middle attack? 
A man-in-the-middle attack occurs when an attacker reroutes communication between two users through the attacker’s computer without the knowledge of the two communicating users. Each user in the communication unknowingly sends traffic to and receives traffic from the attacker, all the while thinking they are communicating only with the intended user.

What is the procedure for revoking a certificate? 
There is a standard procedure that should allow a certificate authority to prevent certificates from being accepted if they are used. Every certificate issuer periodically generates a CRL, which lists all the certificates that should be considered invalid. Every certificate should provide a piece of data called the CRL Distribution Point (CDP) that indicates the location where the CRL can be obtained.

An alternative way for Web browsers to validate the identity of a digital certificate is by using the Online Certificate Status Protocol (OCSP). OCSP allows interactive validation of a certificate by connecting to an OCSP responder, hosted by the Certificate Authority (CA) which signed the digital certificate. Every certificate should provide a pointer to the OCSP responder location through the Authority Information Access (AIA) extension in the certificate. In addition, OCSP stapling allows the Web server itself to provide an OCSP validation response to the client.

OCSP validation is enabled by default on Internet Explorer 7 and later versions of Internet Explorer on supported editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2. On these operating systems, if the OCSP validation check fails, the browser will validate the certificate by contacting the CRL Location.

For more information on certificate revocation checking, see the TechNet article, Certificate Revocation and Status Checking.

What is a Certificate Revocation List (CRL)? 
CRL is a digitally signed list, issued by a CA, that contains a list of certificates issued by the CA and subsequently revoked by the CA. For each individual revoked certificate, the listing includes the serial number of the certificate, the date that the certificate was revoked, and the revocation reason. Applications can perform CRL checking to determine a presented certificate’s revocation status.

What is CRL Distribution Point (CDP)? 
CDP is a certificate extension that indicates where the certificate revocation list for a CA can be retrieved. It can contain none, one, or many HTTP, file, or LDAP URLs.

What is Online Certificate Status Protocol (OCSP)? 
OCSP is a protocol that allows real-time validation of a certificate’s status. Typically, an OCSP responder replies with the revocation status based on the CRL retrieved from the CA.

What is Microsoft doing to help with resolving this issue? 
Although this issue does not result from an issue in any Microsoft product, we have nevertheless updated the Certificate Trust List to remove the trust in the DigiNotar root certificate. Microsoft will continue to investigate this issue and may release a future update to protect customers.

How do I know if I’ve encountered an invalid certificate error? 
When Internet Explorer encounters an invalid certificate, users are presented with a Web page that says, "There is a problem with this website’s security certificate." Users are encouraged to close the Web page and navigate away from the site when this warning message appears.

Users are only presented this message when the certificate is determined to be invalid, for instance when the user has Certificate Revocation List (CRL) or Online Certificate Status Protocol (OCSP) validation enabled. OCSP validation is enabled by default on Internet Explorer 7 and later versions of Internet Explorer on supported editions of Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2.

For supported releases of Microsoft Windows

The majority of customers have automatic updating enabled and will not need to take any action because the KB2616676 update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install the KB2616676 update manually, Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service. For more information on how to manually apply the update, see Microsoft Knowledge Base Article 2616676.

Although the KB2616676 update replaces the KB2607712 update, the KB2607712 update is not a prerequisite for the KB2616676 update. Regardless of whether or not the KB2607712 update has been applied, customers should apply the KB2616676 update to address the issue described in this advisory. Customers who apply the KB2616676 update do not need to apply the KB2607712 update.