Improperly Issued Digital Certificates Could Allow Spoofing
Published: March 24, 2015 | Updated: March 26, 2015
Microsoft is aware of digital certificates that were improperly issued from the subordinate CA, MCS Holdings, which could be used in attempts to spoof content, perform phishing attacks, or perform man-in-the-middle attacks. The improperly issued certificates cannot be used to issue other certificates, impersonate other domains, or sign code. This issue affects all supported releases of Microsoft Windows.
To help protect customers from the potentially fraudulent use of these improperly issued certificates, Microsoft is updating the Certificate Trust list (CTL) to remove the trust of the subordinate CA certificate. The trusted root Certificate Authority, the China Internet Network Information Center (CNNIC), has also revoked the certificate of the subordinate CA. For more information about these certificates, see the Frequently Asked Questions section of this advisory.
Recommendation. Please see the Suggested Actions section of this advisory for instructions on applying an update for specific releases of Microsoft Windows.
For more information about this issue, see the following references:
|Microsoft Knowledge Base Article||3050995|
This advisory discusses the following software.
|Windows Server 2003 Service Pack 2|
|Windows Server 2003 x64 Edition Service Pack 2|
|Windows Server 2003 with SP2 for Itanium-based Systems|
|Windows Vista Service Pack 2|
|Windows Vista x64 Edition Service Pack 2|
|Windows Server 2008 for 32-bit Systems Service Pack 2|
|Windows Server 2008 for x64-based Systems Service Pack 2|
|Windows Server 2008 for Itanium-based Systems Service Pack 2|
|Windows 7 for 32-bit Systems Service Pack 1|
|Windows 7 for x64-based Systems Service Pack 1|
|Windows Server 2008 R2 for x64-based Systems Service Pack 1|
|Windows Server 2008 R2 for Itanium-based Systems Service Pack 1|
|Windows 8 for 32-bit Systems|
|Windows 8 for x64-based Systems|
|Windows Server 2012|
|Windows 8.1 for 32-bit Systems|
|Windows 8.1 for x64-based Systems|
|Windows Server 2012 R2|
|Windows RT 8.1|
|Server Core installation option|
|Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)|
|Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)|
|Windows Server 2008 R2 for x64-based Systems (Server Core installation)|
|Windows Server 2012 (Server Core installation)|
|Windows Server 2012 R2 (Server Core installation)|
|Windows Phone 8|
|Windows Phone 8.1|
**What is the scope of the advisory?**
The purpose of this advisory is to notify customers that MCS Holdings improperly issued SSL certificates for multiple sites including Google web properties. These SSL certificates could be used to spoof content, perform phishing attacks, or perform man-in-the-middle attacks against web properties. The subordinate CA may also have been used to issue certificates for other, currently unknown sites, which could be subject to similar attacks.
**What caused the issue?**
The issue was caused by MCS Holdings, a subordinate CA, improperly issuing domain certificates to entities other than their owners. The MCS Holdings authority is subordinated to the China Internet Network Information Center (CNNIC), which is a CA present in the Trusted Root Certification Authorities Store.
**Does this update address any other digital certificates?**
Yes, in addition to addressing the certificates described in this advisory, this update is cumulative and includes digital certificates described in previous advisories:
– [Microsoft Security Advisory 3046310](http://technet.microsoft.com/security/advisory/3046310)
– [Microsoft Security Advisory 2982792](http://technet.microsoft.com/security/advisory/2982792)
– [Microsoft Security Advisory 2916652](http://technet.microsoft.com/security/advisory/2916652)
– [Microsoft Security Advisory 2798897](http://technet.microsoft.com/security/advisory/2798897)
– [Microsoft Security Advisory 2728973](http://technet.microsoft.com/security/advisory/2728973)
– [Microsoft Security Advisory 2718704](http://technet.microsoft.com/security/advisory/2718704)
– [Microsoft Security Advisory 2641690](http://technet.microsoft.com/security/advisory/2641690)
– [Microsoft Security Advisory 2607712](http://technet.microsoft.com/security/advisory/2607712)
– [Microsoft Security Advisory 2524375](http://technet.microsoft.com/security/advisory/2524375)
**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](http://msdn.microsoft.com/en-us/library/92f9ye3s.aspx), 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](http://msdn.microsoft.com/library/aa376546).
**What might an attacker do with these certificates?**
An attacker could use these certificates to spoof content, perform phishing attacks, or perform man-in-the-middle attacks against the following web properties:
**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 Microsoft doing to help with resolving this issue?**
Although this issue does not result from an issue in any Microsoft product, we are nevertheless updating the CTL and providing an update to help protect customers. Microsoft will continue to investigate this issue and may make future changes to the CTL or release a future update to help protect customers.
**After applying the update, how can I verify the certificates in the Microsoft Untrusted Certificates Store?**
For Windows Vista, Windows 7, Windows Server 2008, and Windows Server 2008 R2 systems that are using the automatic updater of revoked certificates (see [Microsoft Knowledge Base Article 2677070](http://support.microsoft.com/kb/2677070) for details), and for Windows 8, Windows 8.1, Windows RT, Windows RT 8.1, Windows Server 2012, and Windows Server 2012 R2 systems, you can check the Application log in the Event Viewer for an entry with the following values:
– Source: CAPI2
– Level: Information
– Event ID: 4112
– Description: Successful auto update of disallowed certificate list with effective date: Monday, March 23, 2015 (or later).
For systems not using the automatic updater of revoked certificates, in the **Certificates MMC snap-in**, verify that the following certificate has been added to the **Untrusted Certificates** folder:
|MCSHOLDING TEST||CNNIC ROOT||e1 f3 59 1e 76 98 65 c4 e4 47 ac c3 7e af c9 e2 bf e4 c5 76|
**Note** For information on how to view certificates with the MMC Snap-in, see the MSDN article, [How to: View Certificates with the MMC Snap-in](http://msdn.microsoft.com/en-us/library/ms788967.aspx).
**Apply the update for supported releases of Microsoft Windows**
An automatic updater of revoked certificates is included in supported editions of Windows 8, Windows Server 2012, Windows RT, Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2, and for devices running Windows Phone 8 and Windows Phone 8.1. For these operating systems or devices, customers do not need to take any action, because the CTL will be updated automatically.
For systems running Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2 that are using the automatic updater of revoked certificates (see [Microsoft Knowledge Base Article 2677070](http://support.microsoft.com/kb/2677070) for details), customers do not need to take any action, because these systems will be automatically protected.
For customers running Windows Server 2003, Microsoft recommends applying the 3050995 update immediately using update management software, by checking for updates using the [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747) service, or by downloading and applying the update manually (see [Microsoft Knowledge Base Article 3050995](http://support.microsoft.com/kb/3050995) for details).
### Additional Suggested Actions
– **Protect your PC**
We continue to encourage customers to follow our Protect Your Computer guidance of enabling a firewall, getting software updates and installing antivirus software. For more information, see [Microsoft Safety & Security Center](http://www.microsoft.com/security/default.aspx).
– **Keep Microsoft Software Updated**
Users running Microsoft software should apply the latest Microsoft security updates to help make sure that their computers are as protected as possible. If you are not sure whether your software is up to date, visit [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747), scan your computer for available updates, and install any high-priority updates that are offered to you. If you have automatic updating enabled and configured to provide updates for Microsoft products, the updates are delivered to you when they are released, but you should verify that they are installed.
– You can provide feedback by completing the Microsoft Help and Support form, [Customer Service Contact Us](http://support.microsoft.com/kb/?scid=sw;en;1257&showpage=1&ws=technet&sd=tech).
– Customers in the United States and Canada can receive technical support from [Security Support](http://go.microsoft.com/fwlink/?linkid=21131). For more information, see [Microsoft Help and Support](http://support.microsoft.com/).
– International customers can receive support from their local Microsoft subsidiaries. For more information, see [International Support](http://go.microsoft.com/fwlink/?linkid=21155).
– [Microsoft TechNet Security](http://go.microsoft.com/fwlink/?linkid=21132) provides additional information about security in Microsoft products.
The information provided in this advisory is provided “as is” without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
– V1.0 (March 24, 2015): Advisory published.
– V2.0 (March 26, 2015): Advisory rereleased to announce that the update for supported editions of Windows Server 2003 is now available. See [Microsoft Knowledge Base Article 3050995](http://support.microsoft.com/kb/3050995) for more information and download links.
*Page generated 2015-03-26 10:03Z-07:00.*